[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libqt3 and soname problems...



On Sep 12, 2003 at 08:11, Ulrich Eckhardt praised the llamas by saying:
> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> 
> On Thursday 11 September 2003 01:32, Adam Majer wrote:
> > Since Qt is a C++ library, the soname Qt needs to get bumped *every*
> > time a class is changed - that is, a function is added, deleted OR
> > changed. Well, at least the virtual classes AFAIK.
> 
> There is no such thing as a virtual class, you mean virtual function.
> That just as a side note.
> 
> Let me also suggest a thread in comp.lang.c++.moderated called "Does
> adding new methods to a class require recompliation". It turns out
> that you are invoking behaviour not defined by the C++ standard, but
> that it works for many cases.
> 
> Also, I seem to remember that either KDE or Qt had the rules what not
> to do in order to remain backward compatible in their
> coding-guidelines.
> 
http://developer.kde.org/documentation/library/kdeqt/kde3arch/devel-binarycompatibility.html

> I don't think that 3.1 is supposed to be binary compatible with 3.2,
> but I don't really know. I think that 3.2.2 is supposed to be
> compatible with 3.2.1 though.
> 
As I understand it, 3.x should be binary compatible with any other 3.x
release. 4.x will not be binary compatible with 3.x.

-- 
David Pashley
david@davidpashley.com
Nihil curo de ista tua stulta superstitione.

Attachment: pgpB0OhzxOCaV.pgp
Description: PGP signature


Reply to: