Re: [Jackit-devel] latest CVS commit

Paul Davis <[email protected]> writes:

>>> If anyone has a client that calls jack_create_thread(), the API has
>>> changed very, very slightly.

That is like being "a little bit pregnant", right?

>>How are we supposed to deal with the binary incompatibility?
>
> if you can suggest a way around this, i'm all ears. it has no impact
> on ordinary 99%+ of all clients whatsoever.

The only broken client I know about for sure is JAMin.  But, I expect
it is used by more than 1% of JACK users.  Breaking it will probably
affect at least as many people as were inconvenienced by freewheeling
problems under Linux 2.4.

Existing versions of JAMin will work correctly (after recompilation)
if jack_create_client() is undefined.  But, you made the mistake of
changing the function prototype without changing its name.  That
leaves no reasonable way to even release a new version of JAMin that
works with both old and new JACK releases.  That is unacceptable, IMO.
I was just about to make a new JAMin release today.  I would have been
seriously annoyed had you waited until tomorrow to break it.  :-/

This whole change is poorly timed and something of an overreaction.
Introducing binary and source compatibility surely does more harm than
good.  It's going to take us at least another month or two to smoke
out all the other problems inadvertantly introduced by this fix.
Meanwhile, there are significant JACK enhancements that will not be
widely available because of it.
-- 
  joq


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