|Paradigm(s)||Multi-paradigm: prototype-based, functional, imperative, scripting|
|Designed by||Brendan Eich, Ecma International|
|Typing discipline||Duck, weak, dynamic|
|Influenced by||Self, HyperTalk, AWK, C, Perl, Python, Java, Scheme|
|Internet media type||
|Developed by||Sun Microsystems,
|Initial release||June 1997|
|Type of format||Scripting language|
|Part of a series on|
|Lists of Frameworks and Libraries|
- 1 History
- 2 Versions
- 3 Features
- 4 Syntax
- 5 ECMAScript, 4th Edition
- 6 ECMAScript, 5th Edition
- 7 ECMAScript Harmony (6th Edition)
- 8 Implementations
- 9 Version correspondence
- 10 Conformance tests
- 11 See also
- 12 References
- 13 External links
Microsoft delivered JScript to Ecma International for standardization and the work on the specification, ECMA-262, began in November 1996. The first edition of ECMA-262 was adopted by the Ecma General Assembly of June 1997. Several editions of the language standard have been published since then.
ECMAScript is the name of the scripting language standardized in ECMA-262. The name "ECMAScript" was a compromise between the organizations involved in standardizing the language, especially Netscape and Microsoft, whose disputes dominated the early standards sessions. Eich commented that "ECMAScript was always an unwanted trade name that sounds like a skin disease."
There are five editions of ECMA-262 published. Work on a future edition, codenamed "Harmony", is in progress.
|Edition||Date published||Changes from prior edition||Editor|
|1||June 1997||First edition||Guy L. Steele, Jr.|
|2||June 1998||Editorial changes to keep the specification fully aligned with ISO/IEC 16262 international standard||Mike Cowlishaw|
|3||December 1999||Added regular expressions, better string handling, new control statements, try/catch exception handling, tighter definition of errors, formatting for numeric output and other enhancements||Mike Cowlishaw|
|4||Abandoned||Fourth Edition was abandoned, due to political differences concerning language complexity. Many features proposed for the Fourth Edition have been completely dropped; some are proposed for ECMAScript Harmony.|
|5||December 2009||Adds "strict mode", a subset intended to provide more thorough error checking and avoid error-prone constructs. Clarifies many ambiguities in the 3rd edition specification, and accommodates behaviour of real-world implementations that differed consistently from that specification. Adds some new features, such as getters and setters, library support for JSON, and more complete reflection on object properties.||Pratap Lakshman, Allen Wirfs-Brock|
|5.1||June 2011||This edition 5.1 of the ECMAScript Standard is fully aligned with third edition of the international standard ISO/IEC 16262:2011||Pratap Lakshman, Allen Wirfs-Brock|
|6||Work in progress||The Sixth Edition adds significant new syntax for writing complex applications, including classes and modules, but defines them semantically in the same terms as ECMAScript 5 strict mode. Other new features include iterators and
|7||Work in progress||The Seventh Edition is in a very early stage of development, but is intended to continue the themes of language reform, code isolation, control of effects and library/tool enabling from ES6. New features proposed include promises/concurrency, number and math enhancements, guards and trademarks (an alternative to static typing), operator overloading, value types (first-class number-like objects), new record structures (records, tuples and typed arrays), pattern matching, and traits.|
In June 2004, Ecma International published ECMA-357 standard, defining an extension to ECMAScript, known as ECMAScript for XML (E4X).
Ecma also defined a "Compact Profile" for ECMAScript — known as ES-CP, or ECMA 327 — which is designed for resource-constrained devices. Several of the dynamic features of ECMAScript (such as the
eval function) are made optional, thus allowing the runtime to make more assumptions about the behaviour of programs and therefore make more performance trade-offs when running the code. The HD DVD standard was one place where the ECMAScript Compact Profile was used in favour of full ECMAScript to reduce processing and memory needs on devices.
ECMAScript, 4th Edition
The proposed fourth edition of ECMA-262 (ECMAScript 4 or ES4) would have been the first major update to ECMAScript since the third edition was published in 1999. The specification (along with a reference implementation) was originally targeted for completion by October 2008. An overview of the language was released by the working group on October 22, 2007.
As of August 2008, the ECMAScript 4th edition proposal has been scaled back into a project codenamed ECMAScript Harmony.
Features under discussion
Features under discussion for a future edition (originally "ECMAScript 4"; now ECMAScript Harmony) include:
- A module system
- Optional type annotations and static typing, probably using a structural type system
- Generators and iterators
- Destructuring assignment
- Algebraic data types
The intent of these features is partly to better support programming in the large, and to allow sacrificing some of the script's ability to be dynamic to improve performance. For example, Tamarin — the virtual machine for ActionScript developed and open sourced by Adobe — has just-in-time compilation (JIT) support for certain classes of scripts.
Bug fixes and backwards compatibility
In addition to introducing new features, some ES3 bugs were proposed to be fixed in edition 4. These fixes and others, and support for JSON encoding/decoding, have been folded into the ECMAScript, 5th Edition specification.
ECMAScript, 5th Edition
Yahoo, Microsoft, Google, and other 4th edition dissenters formed their own subcommittee to design a less ambitious update of ECMAScript 3, tentatively named ECMAScript 3.1. This edition would focus on security and library updates with a large emphasis on compatibility. After the aforementioned public sparring, the ECMAScript 3.1 and ECMAScript 4 teams agreed on a compromise: the two editions would be worked on, in parallel, with coordination between the teams to ensure that ECMAScript 3.1 remains a strict subset of ECMAScript 4 in both semantics and syntax.
However, the differing philosophies in each team resulted in repeated breakages of the subset rule, and it remained doubtful that the ECMAScript 4 dissenters would ever support or implement ECMAScript 4 in the future. After over a year since the disagreement over the future of ECMAScript within the Ecma Technical Committee 39, the two teams reached a new compromise in July 2008: Brendan Eich announced that Ecma TC39 would focus work on the ECMAScript 3.1 (later renamed to ECMAScript, 5th Edition) project with full collaboration of all parties, and vendors would target at least two interoperable implementations by early 2009. In April 2009, Ecma TC39 published the "final" draft of the 5th edition and announced that testing of interoperable implementations was expected to be completed by mid-July. On December 3, 2009, ECMA-262 5th edition was published.
ECMAScript Harmony (6th Edition)
|This article is outdated. (December 2013)|
In the July 2008 announcement, Eich also stated that the ECMAScript 4 proposal would be superseded by a new project, code-named ECMAScript Harmony. ECMAScript Harmony names the agreed design trajectory of post-ES5 editions. It will include syntactic extensions, but the changes will be more modest than ECMAScript 4 in both semantic and syntactic innovation. Packages, namespaces, and early binding from ECMAScript 4 are no longer included for planned releases. In addition, other goals and ideas from ECMAScript 4 are being rephrased to keep consensus in the committee; these include a notion of classes based on ECMAScript, 5th Edition (being an update to ECMAScript, 3rd edition).
|Application-implementation||Implementation and latest version||ECMAScript edition|
|Internet Explorer, the Trident layout engine||JScript 9.0||ECMA-262, edition 5|
|Java||Nashorn 1.8.0[d 6]||ECMA-262, edition 5.1[d 7]|
|Opera||ECMAScript[d 8]||ECMA-262, edition 5[d 9]|
|RemObjects Script for .NET||ECMAScript||ECMA-262, edition 5|
|Appweb Web Server, Samba 4||Ejscript 0.9.9||ECMA-262, edition 3[d 12]|
|Microsoft .NET Framework||JScript .NET 8.0||ECMA-262, edition 3[d 13]|
|Adobe Flash and Adobe Flex||ActionScript 3||ECMA-262, edition 3[d 14]|
|Adobe Creative Suite products: InDesign, Illustrator,
||ExtendScript||ECMA-262, edition 3|
|General purpose scripting language||DMDScript 1.15||ECMA-262|
|CriScript, JScript for game platforms||CriScript 0.91.0||ECMA-262, edition 3|
|iCab||InScript 3.22 (abandoned)||ECMA-262, edition 3|
|KDE||QtScript||ECMA-262, edition 3|
|Caja||ECMA-262, edition 3[d 19]|
|Objective-J||ECMA-262, edition 3|
|WMLScript||ECMA-262, edition 3|
- SpiderMonkey already supports a wide range of upcoming features: ECMAScript 6 support in Mozilla
- Provides ECMAScript 5.1 implementation as well as some extensions to ease Java integration
- Full ECMAScript 5.1 support in Opera 11.51+ : .
- Commits marked with ES6 are implementations of ES6 features: http://quickgit.kde.org/?p=kjs.git&a=shortlog
- This implementation asserts to support some extensions proposed in drafts of ECMAScript edition 4 (and now ECMAScript Harmony): Ejscript Overview.
- Microsoft asserts that JScript 8.0 supports "almost all of the features of the ECMAScript Edition 3 Language Specification" but does not list the unsupported features.
- In addition to supporting ECMA-262 edition 3, ActionScript 3 also included support for extensions proposed in drafts of ECMAScript edition 4: The Kiwi Project: AS3 language 101 for C/C++ coders.
- As of version 4, OpenLaszlo implements standard ECMAScript edition 3 with some extensions proposed in drafts of ECMAScript edition 4: OpenLaszlo 4.
- Caja emulates strict mode as specified in the ECMAScript edition 5 draft.
|1.0 (Netscape 2.0, March 1996)||1.0 (IE 3.0 - early versions, August 1996)|
|1.1 (Netscape 3.0, August 1996)||2.0 (IE 3.0 - later versions, January 1997)|
|1.2 (Netscape 4.0-4.05, June 1997)|
|1.3 (Netscape 4.06-4.7x, October 1998)||3.0 (IE 4.0, Oct 1997)||Edition 1 (June 1997) / Edition 2 (June 1998)|
|1.4 (Netscape Server only)||4.0 (Visual Studio 6, no IE release)|
|5.0 (IE 5.0, March 1999)|
|5.1 (IE 5.01)|
|1.5 (Netscape 6.0, Nov 2000; also
later Netscape and Mozilla releases)
|5.5 (IE 5.5, July 2000)||Edition 3 (December 1999)|
|5.6 (IE 6.0, October 2001)|
|1.6 (Gecko 1.8, Firefox 1.5, November 2005)||Edition 3, with some compliant enhancements: ECMAScript for XML (E4X),
|JScript .NET (ASP.NET; no IE release)||(JScript .NET is said to have been designed with the participation of other Ecma members)|
Development of Test262 is a project of Ecma Technical Committee 39 (TC39). The testing framework and individual tests are created by member organizations of TC39 and contributed to Ecma for use in Test262.
Important contributions were made by Google (Sputnik testsuite) and Microsoft who both contributed thousands of tests. The Test262 testsuite already contains more than 11,000 tests and is being developed further as of 2013[update].
The following table shows current conformance results of browser products. Lower scores are better, although scores can not be compared as tests are not weighted. Also, be aware that Test262 itself is likely to contain bugs which may impact a browser's score. So browsers with a score significantly lower than the current test suite bug count may not necessarily do better then those with a higher one.
|Product||Latest Stable||Test262 failed||Preview/Beta||Test262 failed||Alpha||Test262 failed||Nightly||Test262 failed|
|Google Chrome||38.0.2125.104 m||8/11552||39.0.2171.27 beta-m||8/11552||40.0.2188.2 dev-m||11/11552||40.0.2191.0 canary||11/11552|
|Mozilla Firefox||33.0||53/11552||34.0 Beta 1||74/11552||35.0a2 (2014-10-18)||109/11552||36.0a1 (2014-10-18)||109/11552|
|Internet Explorer||11.0.13 (11.0.9600.17358)||8/11552|
|Opera||25.0.1614.50||8/11552||beta 25.0.1614.35||8/11552||developer 26.0.1655.0||8/11552|
|12.17 / 16 (Presto)||10/11552|
- Comparison of layout engines (ECMAScript)
- Dart (programming language)
- Document Object Model (DOM)
- ECMAScript for XML (E4X)
- List of ECMAScript engines
- Qt Meta (or Modeling) Language (QML)
- "Press Release". Web.archive.org. Archived from the original on 2007-09-16. Retrieved 2013-10-31.
- [dead link]
- "Press Release". Web.archive.org. Archived from the original on 1998-12-03. Retrieved 2013-10-31.
- "Will there be a suggested file suffix for es4?". Mail.mozilla.org. 2006-10-03. Retrieved 2013-10-31.
- "strawman:strawman [ES Wiki]". Wiki.ecmascript.org. 2013-09-18. Retrieved 2013-10-31.
- "About". ECMAScript. Retrieved 2009-12-17.
- "ES4 overview paper released". Mail.mozilla.org. Retrieved 2013-10-31.
- "Compatibility Between ES3 and Proposed ES4". Ecmascript.org. Retrieved 2013-10-31.
- "ECMAScript 3 and Beyond - IEBlog - Site Home - MSDN Blogs". Blogs.msdn.com. 2007-10-30. Retrieved 2013-10-31.
- "What I think about ES4. - Albatross! - Site Home - MSDN Blogs". Blogs.msdn.com. 2007-10-31. Retrieved 2013-10-31.
- "Open letter to Chris Wilson". Brendan Eich. 2007-10-31. Retrieved 2013-10-31.
- "ECMAScript Harmony". Mail.mozilla.org. Retrieved 2013-10-31.
- "Ecma International finalises major revision of ECMAScript". Ecma International. 2009-04-09. Retrieved 2009-05-22.
- "Ecma latest news". Ecma-international.org. Retrieved 2013-10-31.
- John Resig. "John Resig - ECMAScript Harmony". Ejohn.org. Retrieved 2013-10-31.
- harmony:specification_drafts [ES Wiki]. Wiki.ecmascript.org. Retrieved on 2013-10-23.
- . Twitter. Retrieved on 2014-07-31.
- "Welcome to TypeScript". Typescriptlang.org. Retrieved 2013-10-31.
- "Version Information (JScript)". Msdn.microsoft.com. Retrieved 2009-12-17.
- "Introducing JScript .NET". Microsoft.com. Retrieved 2010-01-12.
- "ECMAScript Language – test262". Test262.ecmascript.org. Retrieved 2013-10-31.
- Schuster, Tom. "Bug 1453". ecmascript.org bug database. Retrieved 12 October 2014.
- ISO Standard
- Ecma Standards
- ECMA-290 ECMAScript Components Specification (June 1999)
- ECMA-327 ECMAScript 3rd Edition Compact Profile (June 2001)
- ECMA-357 ECMAScript for XML (E4X) Specification (June 2004)