The rationale for separation is that programmatic output (everything working 
fine, no messages) goes to stdout so it can be piped from one UNIX command 
to another, whereas error notices and such go to stderr so they do not get 
mixed up with programmatic output.

It is a moot point with message callbacks, or rather to be consistent there 
should be 2, one for stderr and one for stdout.

We have learned how to pipe both stdout and stderr to the same file, so a 
code difference between Csound and Csound API should not be required. More 
consistency in the code is probably a good idea.

----- Original Message ----- 
From: "Anthony Kozar" 
To: "New Csound Developer list" 
Sent: Tuesday, January 25, 2005 8:06 PM
Subject: Re: [Cs-dev] Unbuffered Output


> On 1/25/05 9:36 AM, gogins@pipeline.com  etched in
> stone:
>
>> I understand your point with the utilities. However this is a problem 
>> with
>> Csound itself. Some consoles won't print stderr.
>
> OK.  I guess my question then is which messages are going to which place 
> and
> what is the rational for the separation?  What possible advantages (if 
> any)
> would we be losing by doing this?
>
>> Some people prefer to pipe
>> all Csound messages to a file;
>
> hmmm ... this seems to work OK for me ... or at least I don't remember a
> problem.
>
> Isn't printf redefined as err_printf anyways?  And does this become a moot
> point in Cs5 when using the Message callbacks in the API?
>
> Sorry, I am not too familiar with all of the specifics.
>
>> I don't know how to pipe both stdout and
>> stderr to the same file. We could #ifdef this so the stub library prints
>> output to stdout and messages to stderr, and the csound library prints 
>> both
>> messages and output to stdout.
>
> I could probably live with this change.  Cannot anticipate any problems at
> this moment.
>
> Anthony Kozar
> anthony.kozar@utoledo.edu
> http://akozar.spymac.net/
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net