That is correct. In software design, normally an "error" means that the 
program HAS FAILED or WILL PROBABLY FAIL. A "warning" normally means that 
something unexpected has happened, but that the program will PROBABLY 
SUCCEED.

Regards,
Mike

----- Original Message ----- 
From: "Art Hunkins" 
To: "Developer discussions" 
Sent: Saturday, December 15, 2007 7:17 PM
Subject: Re: [Cs-dev] Default file locations


>I gather that Csound tries to load all standard plugins (and libraries?) at
> startup even if your .csd has no need of them - and issues WARNING 
> messages
> (or worse) if it can't find them.
>
> Then it seems that Csound will procede normally if said plugins are not
> actually required. However, it will be disastrous if expected libraries 
> are
> not available.
>
> Is this correct?
>
> Art Hunkins
>
> ----- Original Message ----- 
> From: "Anthony Kozar" 
> To: "Csound Developer list" 
> Sent: Saturday, December 15, 2007 4:09 PM
> Subject: Re: [Cs-dev] Default file locations
>
>
>> If plugins are searched for in the current directory, then yes, I would
>> expect a lot of those warnings.
>>
>> I think that these messages are useless unless someone is developing a
>> plugin.  I too would like to see them removed or changed so that they 
>> only
>> print with --verbose (or a similar mechanism).
>>
>> The problem is that plugins are loaded _before_ the Csound command line 
>> is
>> processed (and a host application might not even be intending to call
>> csoundCompile() after csoundPreCompile()).  So I am not sure how to turn
>> these messages off by default and still be able to enable them somehow.
>>
>> Any suggestions?
>>
>> I hate to suggest it ... but an environment variable would work.  Another
>> problem I think is that the message callback cannot be set before calling
>> csoundPreCompile (?) so host apps can't catch these messages.  This is
>> especially noticeable on OS 9 where these is no console to view them 
>> with.
>>
>> Anthony
>>
>> Art Hunkins wrote on 12/15/07 3:07 PM:
>>
>>> It would certainly be nice if on Windows the search, by default, would 
>>> be
>>> in
>>> the current directory. (Personally, I like to run everything out of the
>>> current directory, with no environment variables.) I wonder if this is
>>> the
>>> source for the many WARNING messages at the beginning of a Csound run -
>>> as
>>> in "xxxxx is not a plugin". It would be so nice if these would 
>>> disappear.
>>
>>
>> -------------------------------------------------------------------------
>> SF.Net email is sponsored by:
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services
>> for just about anything Open Source.
>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net