Csound Csound-dev Csound-tekno Search About

[Cs-dev] API version

Date2008-12-14 20:20
Fromjpff
Subject[Cs-dev] API version
I am still unclear on this; is it the major version that should be
incremented?

==John ffitch

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2008-12-14 22:49
FromAnthony Kozar
SubjectRe: [Cs-dev] API version
If we are going to go through with this, then the API major version should
be changed to 2 and the minor version to 0 (zero).

I still have reservations about this whole matter and there has not been a
lot of discussion about it in my opinion.

Even if the dynamic linker on all platforms takes care of ensuring that
clients are not linked with incompatible versions of the library, from the
user's standpoint, any API version 1 applications will appear to be broken
when the version 2 library is installed instead of (or over top of) the
version 1 library.  As an example, we already have a lot of confusion on Mac
OS X over which Csound package to install for use with MacCsound.  New users
who install MacCsound and Csound 5.10 (API 2) will see MacCsound bounce in
their dock a few times when launched and then mysteriously fail to launch
with NO error message.  (This is a failing of OS X but nevertheless is what
they will see).

In addition, I have verified that the current installer scripts on OS X WILL
delete any old framework before installing a new one.  So, they need to be
modified to allow versions 5.1 and 5.2 of the framework to coexist, but this
will not fix old installers.  (Version 5.1 will have to be installed before
5.2).

Of course I understand that someday we will want to break compatibility and
there will be a good reason to do so.  While not necessary, I always
envisioned that API version 2.0 would correspond with Csound 6.0.  It is my
opinion that the incompatibilities introduced in Csound 5.09 are not worth
the trouble and confusion of incrementing the API version.  However, since
no one seems to want to revert the incompatible changes, and I believe a
majority of the developers have assented, then we have no option but to
increase the API major version.

Just assume that I am writing the dissenting "minority opinion" and lets
gets on with making sure that this change has a minimal impact on Csound
users.

Anthony

jpff wrote on 12/14/08 3:20 PM:

> I am still unclear on this; is it the major version that should be
> incremented?
> 
> ==John ffitch


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net