Keeping binary compatibility

[Michael Pyne]

On Saturday, October 02, 2010 14:11:32 Christoph Feck wrote:
> On Friday 01 October 2010 15:32:41 Lubos Lunak wrote:
> >  as you probably know, the theory is that KDE libraries keep backwards
> > 
> > binary compatibility. As you might or might not know, that is the
> > theory.
> 
> Let me add to the discussion that r1174275 added a virtual to an exported
> class for 4.5.2 and thus breaks binary compatibility. Not sure if the
> JSObject class is supposed to be used outside kdelibs, though.

I've emailed Maks about that and confirmed that although JSObject is 
KJS_EXPORTed, that only for the usage of other parts of kdelibs. The header 
itself is never installed. Third-party users of KJS do so via other official 
wrappers such as KJSEmbed from what I understand.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/release-team/attachments/20101002/306f5f21/attachment.sig