I brought up this issue about a year ago when I working on the new parser. I won't go into all the detail now as it's probably archived on this mailing list, but currently functions really are just single arg/single output opcodes. There's a limitation on what gets counted as a function but that could be changed, and it could be made that any opcode that satisfies the one in/one out rule could be called as a function. Eventually the limit on args could change as well. On 8/24/07, Jacob Joaquin wrote: > > I agree. > > At this point, perhaps the easiest theoretical solution to preserve Csound's > accidental micro temperament is to dump the numbers from the tables to text > files, use gen 23 to read them into a user tables, and then use an UDO for > converting pitch. A few extra modifications would still be required to the > .orcs from the "detune" generation, which in the grand scheme of things, > isn't that big of a deal. > > Is there by any chance that user-defined functions (UDF) are on the table > for future versions of Csound? From a users standpoint, it would be really > easy if one could just override the builtin functions cpspch/oct with UDFs. > > Getting away from cpspch/oct for a moment. The advantages UDFs would bring > to Csound greatly exceed that particular issue. > > I'm just thinking out loud. > > > Best, > Jake > > ---- > The Csound Blog > http://www.thumbuki.com/csound/blog > > > > > > Anthony Kozar wrote: > > > > This is all beginning to sound to me like more work, more complexity, and > > more confusion for a what amounts to a HYPOTHETICAL possibility that > > making > > cpsoct/pch more accurate will actual cause somebody's existing music to > > sound different. > > > > -- > View this message in context: http://www.nabble.com/Inaccuracies-in-cpspch-and-cpsoct-tf4313733.html#a12312943 > Sent from the Csound - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net