} On some implementations the code to open stdout for audio 
} does not exist. In particular the Macintosh machioen does 
} not support it as there is not really a stdin/stdout system 
} on that machine.

Regarding basic i/o stuff this is not strictly true. Your 
remarks in this area suggest to me that you are trying to 
understand the Mac in terms of a unix definition of what an 
operating system is whereas on the Macintosh a unix type 
implementation is just another application and the developer is 
responsible for coming up with the desired behavior. That's the 
difference between a "program" and an "application".

The problem is that Metrowerks' and Symantec's offerings for 
developer tools in the stdio area have been somewhat less 
than stellar, and that MPW used to cost a small fortune. In 
MPW (which is now free btw), I believe you could build Perf 
as an MPW Tool for use with the MPW shell as a scriptable 
"console". Ditto for a sound i/o tool. For someone who has 
coded since the 1960s and familiar with makefiles (not me) 
this would probably be reasonably easy.

For a bit of news that may be of some interest to Macintosh 
Csound developers in general, here's a portion of a recent 
post from one of the core members of the Apple team:

} > Fred Forsman 

} > In order to understand the larger context surrounding our 
} > MrC[pp] compiler effort, it is useful to know that Apple is 
} > working on versions of the gcc/egcs compiler for the Mac OS X 
} > environment.

*

} ..there are no pipes) and on a Mac I woudl assume you were in 
} trouble unless matt or someone did some serious coding.

The "serious coding" part has already been done. Thanks 
Matt. The Perf currently opens a sound file as 
"post-process" while the front end uses AppleEvents to tell 
an arbitrary text editor to open. Currently, Perf receives a 
message to process files by the front end.



Philip


Philip Aker
Composer, Pianist

Suite 13
1405 West 11 Avenue
Vancouver BC
Canada V6H 1K9

philip@vcn.bc.ca