当前位置：文江博客知识库 en-US 文档 Mozilla Projects SpiderMonkey Releases 38

SpiderMonkey 38 编辑

SpiderMonkey 38 is outdated and contains known security vulnerabilities.

These release notes are incomplete.

The Mozilla JavaScript team is pleased to announce the release of SpiderMonkey 38.

SpiderMonkey 38 is the JavaScript engine that shipped in Firefox 38. It continues to improve performance over previous SpiderMonkey releases, with XXX blah blah blah. It also contains new language and API features described in detail below.

Please let us know about your experiences with this release by posting in the mozilla.dev.tech.js-engine newsgroup. Or file bugs at bugzilla.mozilla.org under Product: Core, Component: JavaScript engine.

— Sep 17, 2015

The download url is outdated and SpiderMonkey not RELEASE alone! Get it here mozilla-esr38

You will find it in "Firefox Extended Support Release 38" package on hg release

Platform support

SpiderMonkey 38 is supported on all the platforms where Firefox 38 runs. Compiling it requires a C++ compiler, and the JSAPI can only be used from C++ code. If you are compiling with Microsoft's Visual Studio, note that the minimum supported version is MSVC10/2010.

SpiderMonkey 38 includes a just-in-time compiler (JIT) that compiles JavaScript to machine code, for a significant speed increase. It is supported on x86, x86_64, and ARM architectures. On some other platforms (SPARC, MIPS), the JIT is provided but not supported. On all other platforms the JIT is simply disabled; JavaScript code runs in an interpreter, as in previous versions. It's the same language, just not as fast.

Migrating to SpiderMonkey 38

....

XXX will need updating for actual new GC stuff at time! A major change to SpiderMonkey in 38 is that its APIs support a moving garbage collector. This entailed changing the vast majority of the JSAPI from raw types, such as JS::Value orJS::Value*, to JS::Handle and JS::MutableHandle template types that encapsulate access to the provided value/string/object or its location. The JS::Handle<JS::Value> and JS::MutableHandle<JS::Value> classes have been specialized to implement the same interface as JS::Value, for simplicity and to ease migration pain. Changes to introduce handles to the JSAPI are not individually documented, because of the breadth of the changes involved.

The following features in earlier versions of SpiderMonkey have been dropped.

XXX list removed features here

SpiderMonkey 38 is not binary-compatible with previous releases, nor is it source-code compatible. Many JSAPI types, functions, and callback signatures have changed, though most functions that have changed still have the same names and implement essentially unchanged functionality. Applications will need significant changes, but most of those changes will be detected by the C/C++ compiler, so they are easy to detect and updating the code is a fairly straightforward job. Here is a list of the most significant changes:

....

These and other changes are explained in detail below.

New JavaScript language features

JavaScript 38 includes significant updates to language features, yo.

New C++ APIs

JSAPI is now a C++-only API. Please note that SpiderMonkey reserves the JS:: namespace for itself (and the js:: namespace for internal use).

Obsolete APIs

Deleted APIs

API changes

jschar, a typedef for the standard C++ type char16_t, has been removed. JSAPI functions that used jschar now use char16_t directly. Embedder code should use char16_t, too. (See bug 1063962.)

JS_PreventExtensions now indicates its success or failure in two ways: via return value (as with most JSAPI methods), and via outparam (indicating whether the attempt took effect or not, independent of JSAPI failure). This change better aligns with ECMAScript's [[PreventExtensions]] hook, which generally returns true or false to indicate whether subsequent attempts to add a new property will fail, yet also itself may throw in some cases.

Mozilla has no plans to keep the JSAPI, nor the JSDBGAPI, stable for embedders. We have chosen to concentrate on performance and correctness as primary concerns instead.
JS_THREADSAFE is going away, with future versions supporting only thread-safe builds
A new debugging API is on the way to replace JSD.