Ignore:
Timestamp:
Dec 8, 2008, 10:46:39 PM (16 years ago)
Author:
[email protected]
Message:

Reviewed by Geoff Garen.

<rdar://problem/6166088> Give JSGlobalContextCreate a behavior that is concurrency aware,
and un-deprecate it

  • API/JSContextRef.cpp: (JSGlobalContextCreate):
  • API/JSContextRef.h: Use a unique context group for the context, unless the application was linked against old JavaScriptCore.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/JavaScriptCore/API/JSContextRef.h

    r35901 r39127  
    7272 built-in JavaScript objects, such as Object, Function, String, and Array.
    7373
    74  The created context can only be used on the main thread. JavaScript values cannot be
    75  shared or exchanged between contexts.
     74 In WebKit version 4.0 and later, the context is created in a unique context group.
     75 Therefore, scripts may execute in it concurrently with scripts executing in other contexts.
     76 However, you may not use values created in the context in other contexts.
    7677@param globalObjectClass The class to use when creating the global object. Pass
    7778 NULL to use the default object class.
    7879@result A JSGlobalContext with a global object of class globalObjectClass.
    7980*/
    80 JS_EXPORT JSGlobalContextRef JSGlobalContextCreate(JSClassRef globalObjectClass) AVAILABLE_WEBKIT_VERSION_3_0_AND_LATER_BUT_DEPRECATED_AFTER_WEBKIT_VERSION_3_1;
     81JS_EXPORT JSGlobalContextRef JSGlobalContextCreate(JSClassRef globalObjectClass) AVAILABLE_WEBKIT_VERSION_3_0_AND_LATER;
    8182
    8283/*!
Note: See TracChangeset for help on using the changeset viewer.