On Sat, Feb 27, 2010 at 05:34:34PM -0500, Michael Gogins wrote:

> How does it become non-portable? I don't see that it does that at all.

Because you use Jack-specific opcodes to do audio I/0.

If you want portable Csound code it should use only
generic (interface agnostic) calls to do audio I/O.

Anything specific to Jack (port names, connections,...)
should be in the startup code only, where it is localised
and easy to change/ignore/remove if necessary.

Ciao,

-- 
FA

O tu, che porte, correndo si ?
E guerra e morte !

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net