OK, it sounds like things are now as they should be with respect to stderr, 
stdout, and -o stdout but I will have to see how CsoundVST runs now on 
Linux.

About option parsing, I would not expect .csd filenames to occur in .csd
files, only .orc or .sco filenames.

----- Original Message ----- 
From: "Istvan Varga" 
To: 
Sent: Sunday, February 20, 2005 12:44 PM
Subject: Re: [Cs-dev] Some questions about recent changes


> gogins@pipeline.com wrote:
>
>> I noticed that output now goes to stderr instead of stdout on non-Windows
>> platforms so that "-o stdout" does not get corrupted. This obviously is a
>> good idea, but should it be this way on Windows also?
>
> I do not really care about whether messages are printed to stderr or 
> stdout
> on Windows, so if you prefer stderr, then the check for WIN32 can be 
> removed.
> The only reason for printing to stdout was that the DOS/Windows command 
> line
> does not allow redirection of stderr, only stdout, and -o stdout is not
> available on Win32.
>
>> I also noticed that option parsing was changed to disallow using .orc and
>> .sco names in .csd and .csoundrc files.  However, this breaks some 
>> behavior
>> of CsoundVST, which depends on being able to include .orc and .sco
>> filenames in .csd files. This is because CsoundVST loads and edits .csd
>> files, but it does not perform them as .csd files; it performs them by
>> exporting the .orc and .sco file separately. The reason for this is that 
>> in
>> Python mode, CsoundVST generates the .sco file programmatically, using 
>> the
>> name given on the Csound command line, and it also still exports the .orc
>> file in the usual way.
>
> So, you want orc and sco names in the CSD. Now, if the CSD contains a CSD
> name, should it then be loaded recursively (it may contain a CSD name and
> so on) ? What exact behavior do you expect ?
>
>> But obviously we need to discuss this. Is there something else that 
>> breaks
>> if .orc and .sco filenames are permitted in .csd files?
>
> I will check if the changes introduced any problems.
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


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




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

gogins@pipeline.com wrote:

> About option parsing, I would not expect .csd filenames to occur in .csd
> files, only .orc or .sco filenames.

Could you explain exactly how are .orc and .sco filenames used in a CSD
(an example would be welcome), with all possible combinations in CsOptions
(orc only, sco only, orc&sco, csd etc.) ? Also, how about using orc/sco/csd
names in .csoundrc (you also made that valid), what is the use of that ?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net