I agree with Rory -- let us have a discussion first, here and then add a ticket(s) when there is some agreement. Could also discuss on csound list if it did not put people off Quoting Rory Walsh : > I wouldn't mind seeing the suggestions/discussion here. Although it > will ultimately be in the hands of the dev team, it's nice to have > some dialogue about these things before they are implemented? > > > On 8 April 2014 12:11, joachim heintz wrote: >> i would like to send suggestions about what would be nice to have while >> working with arrays. what is the best place: post it here, or as a >> feature request on github? >> >> best - >> joachim >> >> ------------------------------------------------------------------------------ >> Put Bad Developers to Shame >> Dominate Development with Jenkins Continuous Integration >> Continuously Automate Build, Test & Deployment >> Start a new project now. Try Jenkins in the cloud. >> http://p.sf.net/sfu/13600_Cloudbees >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net