RFC: adding a temporary, non-BC gauranteed, 'private' library .. where?
thiago at kde.org
Thu Apr 23 07:57:22 BST 2009
Thiago Macieira wrote:
>2) don't ever remove it
>And in either case, you have to put the headers in the same place as
> kdeui (i.e., future compatibility) and you have to use a hidden
> namespace to avoid conflicting with the symbols when it does make its
> way to kdeui (à la Animations Solution).
Hmm... you can't move symbols from one library to another (see
src/corelib/xml/qxmlstream.h for information in our attempt). If you
change the symbol name, be it by changing the namespace or removing it,
then the changes are source-compatible but not binary.
It only works as long as those classes are never used in ANY public API.
And like QXmlStreamXXXX classes today, you can't forward-declare them.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel