On Oct 5, 2006, at 01:27, Jeremy Bettis wrote:
I thought that to provide a "stable" ABI, you just can't do these
things:
...
But these things should not cause instabilitity:
Adding a class
Adding a method
Thats wrong. A soname fixes one API, it can be neither extended nor
reduced (nor changed in the behaviour). I already gave the example of
adding a class.
You are mixing up ABIs (or more exactly sonames) with backward
compatible APIs :-) APIs ensure source code compatibility while ABIs
ensure binary compatibility. (you can replace the library and an
arbitary program linked against the specific soname still works)
GNUstep has very good API compatibility but this doesn't help at all
with binary packages.
Greets,
Helge
--
Helge Hess
http://docs.opengroupware.org/Members/helge/
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
