| That is because UDOs are internally treated as instruments. We can look at the diagnostic message, but imo this should be an error not a warning.
On 21 Jan 2012, at 11:36, joachim heintz wrote:
> hi developers -
>
> redefining a UDO returns a warning with the old parser, but an error
> with the new parser. and the error message might point to another
> problem, because it refers to an instrument (which is actually nonsense,
> as far as i see). this is my output for the csd below:
>
> WARNING: redefined opcode: bla
> Parsing successful!
> bla : bla
> error: instr bla redefinedbla : bla
> instr bla uses instrument number 2
> 1 syntax errors in orchestra. compilation invalid
>
> there is no instrument bla, just a udo bla. can you have a look? best -
>
> joachim
>
>
>
>
>
>
> opcode bla, 0, 0
> endop
> opcode bla, 0, 0
> endop
> instr 1
> endin
>
>
> i 1 0 0
>
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |