I find it a little misleading that csoundCompile() returns 0(success)
even when the orchestra contains INIT errors. Should it not return 0
only if everything is well in the world? Anyhow, anyone know how I can
systematically check an orchestra for INIT errors?

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Init & Perf errors are issued when opcodes are instantiated, so they would not
be picked up on compilation. There is an exception: if the init error is in instr0, then
because the code is run immediately after compilation, you will get an error from csoundCompile().

Init & Perf errors can be generated by a combination of orc and sco code (wrong parameters),
or even orc and RT input (midi, events, OSC, …), so it might not be possible to
systematically check an orchestra for them.

========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 11 May 2014, at 00:31, Rory Walsh  wrote:

> I find it a little misleading that csoundCompile() returns 0(success)
> even when the orchestra contains INIT errors. Should it not return 0
> only if everything is well in the world? Anyhow, anyone know how I can
> systematically check an orchestra for INIT errors?
> 
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Victor, that clears that up.

On 11 May 2014 01:40, Victor Lazzarini  wrote:
> Init & Perf errors are issued when opcodes are instantiated, so they would not
> be picked up on compilation. There is an exception: if the init error is in instr0, then
> because the code is run immediately after compilation, you will get an error from csoundCompile().
>
> Init & Perf errors can be generated by a combination of orc and sco code (wrong parameters),
> or even orc and RT input (midi, events, OSC, …), so it might not be possible to
> systematically check an orchestra for them.
>
> ========================
> Dr Victor Lazzarini
> Senior Lecturer
> NUI Maynooth, Ireland
> victor dot lazzarini at nuim dot ie
>
>
>
>
> On 11 May 2014, at 00:31, Rory Walsh  wrote:
>
>> I find it a little misleading that csoundCompile() returns 0(success)
>> even when the orchestra contains INIT errors. Should it not return 0
>> only if everything is well in the world? Anyhow, anyone know how I can
>> systematically check an orchestra for INIT errors?
>>
>> ------------------------------------------------------------------------------
>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
>> • 3 signs your SCM is hindering your productivity
>> • Requirements for releasing software faster
>> • Expert tips and advice for migrating your SCM now
>> http://p.sf.net/sfu/perforce
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cso