Yes, the Csound 5 API requires changes to the source code of opcodes. That's what I was getting at.

-----Original Message-----
From: "John D. Ramsdell" 
Sent: Mar 19, 2005 10:47 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] csound-config for Csound 5

Michael Gogins  writes:

> Csound 5 and Csound 4 are not binary compatible. Wouldn't this create a problem here?
> 
> The binary differences are in the Csound API and in the function
> signatures for opcodes.

Binary compatibility is not the issue, as I'm talking about building
opcodes from their sources, however, if Csound 5 API requires changes
to the source code of opcodes, there will indeed be a problem.

When considering this issue, look at it from the perspective of an
application such as Loris.  If you do not require those applications
to change their code when moving from Csound 4 to 5, then the
csound-config script will allow them to make no changes to their code
base when Csound 5 is released.

John

> 
> -----Original Message-----
> From: "John D. Ramsdell" 
> Sent: Mar 19, 2005 9:35 AM
> To: csound-devel@lists.sourceforge.net
> Subject: [Cs-dev] csound-config for Csound 5
> 
> To all Csound 5 developers, 
> 
> Please add a csound-config script to Csound 5 patterned after the one
> distributed with Csound 4.  If you install a csound-config script into
> the place in which you install binaries, this script will allow users
> of your libraries and headers to easily and automatically configure
> their applications for use with Csound 5.  For applications that use
> only the Csound 4 API, such a script would allow a source version of a
> the application known to work with Csound 4 to automatically detect
> and use Csound 5 whenever it is available.  No modifications to the
> source would be required.  An example of a system that would benefit
> from the addition of a csound-config script is Loris
> . 
> 
> John
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 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


-------------------------------------------------------
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





-------------------------------------------------------
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

Michael Gogins  writes:

> Yes, the Csound 5 API requires changes to the source code of
> opcodes. That's what I was getting at.

Understood now.

John


-------------------------------------------------------
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