JavaScriptCore merge & binary compatibility

[Harri Porten]

On Sun, 16 Feb 2003, Peter Kelly wrote:

> Harri, what are your plans for BIC changes to KJS merged from safari? I 
> seem to recall you or someone else mentioning a new library version to 
> distinguish it from the currently-released kjs but I'm not really clear
> what is supposed to be happening there.

The latest consensus was to accept breaking BC in libkjs without any
renaming nor major version number change (don't let anyone outside of this
list hear this;). The justification is the small number of users -
possibly 0 outside of kdelibs/kdebase.

> I'm currently looking at merging some of the code but I'd like to know 
> what public API's can/can't be merged at this stage & how you think we 
> should approach this.

In regards to API changes I'm still a bit more hesitant than just BIC
changes. The most dramatic one will be the use of Identifier rather than
UString in the extension API but a fallback virtual function should be
possible so that old code will keep compiling.
When it comes to Apple's optimized storage of Numbers I would still like
to present the approach taken in QSA first. It allows for more types to be
stored more efficiently without coding any special excemptions.

What APIs are you thinking of ?

Harri.