Thanks very much, Anthony.

I hope your changes are incorporated into the final release of 5.08.

Presumably this problem may have been partly responsible for the lack of use 
of , as john ff observed.

This correction should be particularly helpful to musician/performers 
presenting live works by others, and who are not otherwise Csound 
practitioners. (I'm sure this group of performers is not large; hopefully, 
with care on our part [dealing with user issues like this one], the group 
will multiply in the future. At least, this is my hope.)

Art Hunkins

----- Original Message ----- 
From: "Anthony Kozar" 
To: "Csound Developer list" 
Sent: Monday, January 28, 2008 11:20 PM
Subject: Re: [Cs-dev] 


> Art Hunkins wrote on 1/28/08 9:38 PM:
>
>> I've been exploring the  tag in WinXP, and it does not seem to
>> behave correctly. Could a developer please check it out?
>
> Yes.  It was broken but I have fixed it now.  (Of course, versions of 
> Csound
> from 5.00 to 5.07 will fail to check this tag correctly, potentially 
> making
> it less useful).
>
> There were two problems.  The first was an internal calculation of the
> version number.  The second was that "Before x.y" and "After x.y" were 
> both
> OK with version x.y where the manual says that they should reject it.  I
> have made the check match what the manual says the behavior should be.
>
>> This is what I've found:
>>
>> I'm running Csound 5.06.
>>
>> The CsVersion code I tested is:
>> 
>> After x.x
>> 
>>
>> Csd's  run fine with the following values for x.x:
>> 4.99, 5.06, 5.07, 5.08, 5.09, 5.6, 5.60, 5.7, 5.8, 5.9
>>
>> The following values stop Csound with a "Decode failed...stopping" 
>> message:
>> 5.70, 5.80, 5.85, 5.89, 5.90, 5.99
>
> Note that 5.80 and 5.8 are not the same.  5.8 is interpreted the same as
> 5.08.  The minor version number of Csound is always supposed to be two
> digits long.
>
>> (Please note as well that a Windows version 5.04.2 exists. Does CsVersion
>> handle this second decimal correctly?)
>
> No.  I am not sure how to modify the check for this in a way that will 
> keep
> it compatible with the currently documented behavior.  (Not that it could
> not be done ... but I don't want to potentially break it again :)
>
>> I'd also recommend that the somewhat cryptic "decode failed" message be
>> changed to:
>> "A version of Csound > x.x is required"
>> or alternately:
>> "A version of Csound < x.x is required".
>
> I have improved the error reporting for this and I will commit all of my
> changes after making some more needed improvements to messages about CSD
> "decoding" errors.
>
> Anthony Kozar
> mailing-lists-1001 AT anthonykozar DOT net
> http://anthonykozar.net/
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The changes have been made and should be in the 5.08 beta, soon to be
released.  I will note that  was broken while developing version
5.00.  So, it should have worked with the 4.xx series and should work in
future releases (I hope!).

Unfortunately, the code that compared version numbers from 5.00 to 5.07
would convert Csound's internal version into something like 5070 for 5.07,
but the  code would read 5.07 as 5007.  So, for example, a
statement like "After 5.07" would pass the check in versions 5.01 through
5.07 when it should not have.  Checking for "After 5.70" instead would
properly exclude those versions, but now will not work with 5.08 through
5.69 as intended.  Thus, there is no good way to correctly check for
versions 5.01 to 5.07 ...

Anthony

Art Hunkins wrote on 1/29/08 10:31 AM:

> I hope your changes are incorporated into the final release of 5.08.
> 
> Presumably this problem may have been partly responsible for the lack of use
> of , as john ff observed.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net