Keeping binary compatibility

Richard Moore richmoore44 at
Sun Oct 3 11:59:48 CEST 2010

On Sat, Oct 2, 2010 at 9:54 PM, Michael Pyne <mpyne at> wrote:
> 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.

Since we don't install the kjsembed headers either, I would guess it
must be JSObject -> KJSEmbed -> Kross.


More information about the release-team mailing list