Bug 20232 - JavaScriptCore API needs a version
Summary: JavaScriptCore API needs a version
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on: 20282
Blocks:
  Show dependency tree / graph
 
Reported: 2008-07-30 13:35 PDT by Christian Dywan
Modified: 2012-02-20 14:40 PST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Dywan 2008-07-30 13:35:03 PDT 
The public interface of JavaScriptCore has no version of its own. The Mac port actually introduced WebKitAvailabillity.h some time ago to share the version number between JavaScriptCore and WebKit. The situation is becoming particularly interesting now since JavaScriptCore gains new API and ports other than Mac cannot check any kind of version number.

For instance JSContextGroupRef was introduced 2008-07-29, "Implement JSContextGroup APIs to make concurrent execution possible for JavaScriptCore clients". The commit intorduced new API and changed behaviour.

I don't know what ports apart from Gtk are actually shipping JavaScriptCore headers as part of their API right now, but a port agnostic version seems like the right solution here.
Comment 1 Martin Robinson 2012-02-20 14:40:19 PST 
JavaScriptCore is now versioned along with WebKitGTK+. If we ever ship a version of JSC separate from WebKitGTK+, it will have it's own versioning.