Yes, I think I or someone else didn't get what you were trying to do with
this distinction. My apologies if it was myself (don't quite remember).

Actually, I would argue against writing to both stdout and stderr. I
personally find that this adds complications and makes it more difficult to
collect printouts to files and such. A long time ago stderr was more
efficient than stdout, but I don't think that is so much the case now, and
even if it proves so, stdout can be configured to print without buffering
just like stderr.

What are your reasons for wanting to print to both stdout and stderr? Would
you object to printing only to one stream, defaulting to stdout?

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Fri,  5 Dec 2003 05:44:00 +0000
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3656] Messages in API


I fail to understand the difference between csoundMessageV and
csoundMessageS.  Is this an implementation of the functions I wanted a
long time ago with Csound being able to distinguish stdout and stderr
style messages?  I cannot see where that is at present (that was
related to csoundMessage0)
==John ffitch


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .