Jump to content

ECMAScript: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m →‎Version correspondence: Removed invalid "below"
Line 147: Line 147:
In the July 2008 announcement, [[Brendan Eich|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).<ref>{{cite web|author=John Resig |url=http://ejohn.org/blog/ecmascript-harmony/ |title=John Resig - ECMAScript Harmony |publisher=Ejohn.org |date= |accessdate=2013-10-31}}</ref>
In the July 2008 announcement, [[Brendan Eich|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).<ref>{{cite web|author=John Resig |url=http://ejohn.org/blog/ecmascript-harmony/ |title=John Resig - ECMAScript Harmony |publisher=Ejohn.org |date= |accessdate=2013-10-31}}</ref>


Drafts of ES.next have been published periodically since July 2011,<ref>[http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts harmony:specification_drafts [ES Wiki&#93;]. Wiki.ecmascript.org. Retrieved on 2013-10-23.</ref> with a target release date of December 2014.<ref>[https://github.com/rwaldron/tc39-notes/blob/48c5d285bf8bf0c4e6e8bb0c02a7c840c01cd2ff/es6/2013-03/mar-13.md#416-current-status-of-es6 tc39-notes/es6/2013-03/mar-13.md at 48c5d285bf8bf0c4e6e8bb0c02a7c840c01cd2ff · rwaldron/tc39-notes]. Github.com. Retrieved on 2014-01-08.</ref>
Drafts of ES.next have been published periodically since July 2011,<ref>[http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts harmony:specification_drafts [ES Wiki&#93;]. Wiki.ecmascript.org. Retrieved on 2013-10-23.</ref> with a target release date of June 2015.<ref>[https://twitter.com/awbjs/status/474662357516689410]. Twitter. Retrieved on 2014-07-31.</ref>


== Implementations ==
== Implementations ==

Revision as of 14:24, 31 July 2014

ECMAScript
ParadigmMulti-paradigm: prototype-based, functional, imperative, scripting
Designed byBrendan Eich, Ecma International
First appeared1997
Typing disciplineDuck, weak, dynamic
Websiteecma-international.org
Major implementations
JavaScript, ActionScript, JScript, QML, QtScript, InScript
Influenced by
Self, HyperTalk, AWK, C, Perl, Python, Java, Scheme
ECMAScript
Filename extensions
.es
Internet media type
application/ecmascript
Developed bySun Microsystems,
Ecma International
Initial releaseJune 1997
Latest release
Edition 5.1
June 2011; 13 years ago (2011-06)
Type of formatScripting language
WebsiteECMA-262, ECMA-290,
ECMA-327, ECMA-357,
ECMA-402

Template:JavaScriptSidebar ECMAScript is the scripting language standardized by Ecma International in the ECMA-262 specification and ISO/IEC 16262. The language is widely used for client-side scripting on the web, in the form of several well-known implementations such as JavaScript, JScript and ActionScript.

History

JavaScript was originally developed by Brendan Eich of Netscape under the name Mocha, later LiveScript, and finally renamed to JavaScript.[1] In December 1995, Sun Microsystems and Netscape announced JavaScript in a press release.[2] In March 1996, Netscape Navigator 2.0 was released, featuring support for JavaScript.

Owing to the widespread success of JavaScript as a client-side scripting language for web pages, Microsoft developed a compatible dialect of the language, naming it JScript to avoid trademark issues. JScript added new date methods to fix the non-Y2K-friendly methods in JavaScript, which were based on the Java Date class.[3] JScript was included in Internet Explorer 3.0, released in August 1996.

Microsoft delivered JScript to Ecma International for standardization and the work on the specification, ECMA-262, began in November 1996.[4] 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. Brendan Eich, the creator of JavaScript, commented that "ECMAScript was always an unwanted trade name that sounds like a skin disease."[5]

While both JavaScript and JScript aim to be compatible with ECMAScript, they also provide additional features not described in the ECMA specifications. [citation needed]

Versions

There are five editions of ECMA-262 published. Work on a future edition, codenamed "Harmony", is in progress.[6]

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.[7] 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 for/of loops, Python-style generators and generator expressions, arrow functions, binary data, collections (maps, sets and weak maps), and proxies (metaprogramming for virtual objects and wrappers). As the first “ECMAScript Harmony” specification, it is also known as “ES6 Harmony”. Allen Wirfs-Brock
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.[8]

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.

Features

Further information: ECMAScript features

The ECMAScript language includes structured, dynamic, functional, and prototype-based features, as officially summarized here.[9]

Syntax

Further information: ECMAScript syntax

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.[10] 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:

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.[11][12] These fixes and others, and support for JSON encoding/decoding, have been folded into the ECMAScript, 5th Edition specification.[13]

History

Work started on Edition 4 after the ES-CP (Compact Profile) specification was completed, and continued for approximately 18 months where slow progress was made balancing the theory of Netscape's JavaScript 2 specification with the implementation experience of Microsoft's JScript .NET. After some time, the focus shifted to the ECMAScript for XML (E4X) standard. The update has not been without controversy. In late 2007, a debate between Eich, later the Mozilla Foundation's CTO, and Chris Wilson, Microsoft's platform architect for Internet Explorer, became public on a number of blogs. Wilson cautioned that because the proposed changes to ECMAScript made it backwards incompatible in some respects to earlier versions of the language, the update amounted to "breaking the Web,"[14] and that stakeholders who opposed the changes were being "hidden from view".[15] Eich responded by stating that Wilson seemed to be "repeating falsehoods in blogs" and denied that there was attempt to suppress dissent and challenged critics to give specific examples of incompatibility.[16] He also pointed out that Microsoft Silverlight and Adobe AIR rely on C# and ActionScript 3 respectively, both of which are larger and more complex than ECMAScript Edition 3.[17]

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.[18][19] 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.[20] On December 3, 2009, ECMA-262 5th edition was published.[21]

ECMAScript Harmony (6th Edition)

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).[22]

Drafts of ES.next have been published periodically since July 2011,[23] with a target release date of June 2015.[24]

Implementations

ECMAScript is supported in many applications, especially web browsers, where it is implemented by JavaScript, or, in the case of Internet Explorer, JScript. Implementations sometimes include extensions to the language, or to the standard library and related application programming interfaces (API) such as the World Wide Web Consortium (W3C) specified Document Object Model (DOM). This means that applications written in one implementation may be incompatible with another, unless they are written to use only a common subset of supported features and APIs.

Application-implementation Implementation and latest version ECMAScript edition
Mozilla Firefox, the Gecko layout engine, SpiderMonkey, and Rhino[d 1] JavaScript 1.8.5[d 2] ECMA-262, edition 5, and features from upcoming 6. [d 3]
Google Chrome, the V8 engine JavaScript[d 2] ECMA-262, edition 5[d 4][d 5]
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
KHTML layout engine, KDE's Konqueror, and Apple Inc.'s Safari[d 10] JavaScript[d 2] ECMA-262, edition 3
Appweb Web Server, Samba 4 Ejscript 0.9.9 ECMA-262, edition 3[d 11]
Microsoft .NET Framework JScript .NET 8.0 ECMA-262, edition 3[d 12]
Adobe Flash and Adobe Flex ActionScript 3 ECMA-262, edition 3[d 13]
Adobe Acrobat JavaScript 1.7[d 14] ECMA-262, edition 3
Adobe Creative Suite products: InDesign, Illustrator,

Photoshop, Bridge, After Effects, Premiere Pro

ExtendScript ECMA-262, edition 3 [citation needed]
General purpose scripting language DMDScript 1.15 ECMA-262
OpenLaszlo JavaScript[d 15] ECMA-262, edition 3[d 16]
CriScript, JScript for game platforms CriScript 0.91.0 ECMA-262, edition 3
iCab InScript 3.22 (abandoned) ECMA-262, edition 3
Max/MSP JavaScript 1.5[d 2] ECMA-262, edition 3
ANT Galio 3 JavaScript 1.5[d 2][d 17] ECMA-262, edition 3
KDE QtScript ECMA-262, edition 3
Caja ECMA-262, edition 3[d 18]
Objective-J ECMA-262, edition 3
WMLScript ECMA-262, edition 3
Compiler-generated JavaScript applications TypeScript[25] ECMA-262, edition 3, 5 and features from upcoming 6.
  1. ^ The Mozilla implementations, (SpiderMonkey in the C++ language, Rhino in the Java language), are used in several third-party programs, including the Yahoo! Widget Engine (Konfabulator) and the Macintosh system-level scripting language JavaScript OSA.
  2. ^ a b c d e "JavaScript" is an ECMAScript variant managed by Mozilla. All non-Mozilla implementations using JavaScript are actually implementing ECMAScript, rather than Javascript. "JavaScript" support generally is meant to describe support for ECMA-262, edition 3, though some—notably Chrome, but also Opera 12 and Internet Explorer 10—target ECMA-262, edition 5.
  3. ^ SpiderMonkey already supports a wide range of upcoming features: ECMAScript 6 support in Mozilla
  4. ^ V8, the JavaScript engine created by Google and used in Chrome, implements ECMAScript as specified in ECMA-262, 5th edition: V8 JavaScript Engine.
  5. ^ Chrome also implements non-ECMAScript-standard extensions to the language which are present in WebKit, in order to maintain compatibility with JavaScriptCore (which is itself based on the KDE KJS library) : V8 JavaScript Engine issue tracker.
  6. ^ Provides ECMAScript 5.1 implementation as well as some extensions to ease Java integration
  7. ^ Full ECMAScript 5.1 support in Opera 11.51+ : [1].
  8. ^ Opera's implementation includes some JavaScript and JScript extensions: ECMAScript support in Opera Presto 2.3
  9. ^ Full ECMAScript (JavaScript) 5.1 support in Opera 11.51+ : [2].
  10. ^ Apple's Safari uses JavaScriptCore which is based on the KDE KJS library.
  11. ^ This implementation asserts to support some extensions proposed in drafts of ECMAScript edition 4 (and now ECMAScript Harmony): Ejscript Overview.
  12. ^ 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.
  13. ^ 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.
  14. ^ Adobe Acrobat 9.0 uses the SpiderMonkey 1.7 engine: JavaScript for Acrobat API Reference
  15. ^ OpenLaszlo both uses an ECMAScript implementation as noted in the Developer's Guide: Appendix B: ECMAScript and can compile down to JavaScript targeted for the browser (the DHTML target).
  16. ^ As of version 4, OpenLaszlo implements standard ECMAScript edition 3 with some extensions proposed in drafts of ECMAScript edition 4: OpenLaszlo 4.
  17. ^ ANT Galio Browser claims support for JavaScript 1.5.
  18. ^ Caja emulates strict mode as specified in the ECMAScript edition 5 draft.

Version correspondence

The following table is based on tedster's history compilation forum post[26] and Microsoft's JScript version information webpage.[27] Items on the same line are approximately the same language.

JavaScript JScript ECMAScript
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), Array extras (e.g. Array.prototype.forEach), Array and String generics (New in JavaScript 1.6)
1.7 (Gecko 1.8.1, Firefox 2, October 2006) Edition 3 plus all JavaScript 1.6 enhancements, plus Pythonic generators and array comprehensions ([a*a for (a in iter)]), block scope with let, destructuring assignment (var [a,b]=[1,2]) (New in JavaScript 1.7)
1.8 (Gecko 1.9, Firefox 3, June 2008) Edition 3 plus all JavaScript 1.7 enhancements, plus expression closures (function(x) x * x), generator expressions, and more (New in JavaScript 1.8)
JScript .NET (ASP.NET; no IE release) (JScript .NET is said to have been designed with the participation of other Ecma members)[28]
JavaScript 2.0 (Work in progress) Harmony (Work in progress; see the section "ECMAScript Harmony").

Conformance tests

In 2010, Ecma International started developing a standards test for Ecma 262 ECMAScript.[29] Test262 is an ECMAScript conformance test suite that can be used to check how closely a JavaScript implementation follows the ECMAScript 5th Edition Specification. The test suite contains thousands of individual tests, each of which tests some specific requirements of the ECMAScript specification.

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. Be aware that Test262 itself may contain bugs which may impact some browsers' scores. So take these figures with a grain of salt.

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.

Results of Test262 (suite version: ES5.1, suite date: 2013-06-13)
Product Latest Stable Test262 failed Preview/Beta Test262 failed Alpha Test262 failed Nightly Test262 failed
Google Chrome 36.0.1985.125 m 10/11578 Beta: 37.0.2062.58 beta-m 10/11578 Dev: 38.0.2107.2 dev-m 10/11578 Canary: 38.0.2108.0 canary 10/11578
Mozilla Firefox 31.0 48/11578 Beta: 32.0b2 48/11578 Aurora: 33.0a2 (2014-07-30) 53/11578 Nightly: 34.0a1 (2014-07-30) 53/11578
31.0 ESR 48/11578
24.7.0 ESR 75/11578
Internet Explorer 11.0.10 (11.0.9600.17207) 7/11578 Dev Channel
Maxthon 4.4.1.2000 10/11578
Opera 23.0.1522.60 (Blink) 10/11578 Next: 24.0.1558.25 10/11578 Developer: 24.0.1558.21 10/11578
12.17 / 12.16 (Presto) 11/11578
Safari 7.0 (9537.71) 8/11578

See also

References

  1. ^ Krill, Paul (2008-06-23). "JavaScript creator ponders past, future | Developer World". InfoWorld. Retrieved 2013-10-31.
  2. ^ "Press Release". Web.archive.org. Archived from the original on 2007-09-16. Retrieved 2013-10-31.
  3. ^ [3][dead link]
  4. ^ "Press Release". Web.archive.org. Archived from the original on 1998-12-03. Retrieved 2013-10-31.
  5. ^ "Will there be a suggested file suffix for es4?". Mail.mozilla.org. 2006-10-03. Retrieved 2013-10-31.
  6. ^ Zakas, Nicholas C. (2011). Professional JavaScript for Web Developers. John Wiley & Sons. ISBN 9781118233092.
  7. ^ "Changes to JavaScript, Part 1: EcmaScript 5". YouTube. 2009-05-18. Retrieved 2013-10-31.
  8. ^ "strawman:strawman [ES Wiki]". Wiki.ecmascript.org. 2013-09-18. Retrieved 2013-10-31.
  9. ^ "About". ECMAScript. Retrieved 2009-12-17.
  10. ^ "ES4 overview paper released". Mail.mozilla.org. Retrieved 2013-10-31.
  11. ^ John Resig. "John Resig - Bug Fixes in JavaScript 2". Ejohn.org. Retrieved 2013-10-31.
  12. ^ "Compatibility Between ES3 and Proposed ES4" (PDF). Ecmascript.org. Retrieved 2013-10-31.
  13. ^ [4]
  14. ^ "ECMAScript 3 and Beyond - IEBlog - Site Home - MSDN Blogs". Blogs.msdn.com. 2007-10-30. Retrieved 2013-10-31.
  15. ^ "What I think about ES4. - Albatross! - Site Home - MSDN Blogs". Blogs.msdn.com. 2007-10-31. Retrieved 2013-10-31.
  16. ^ "Open letter to Chris Wilson". Brendan Eich. 2007-10-31. Retrieved 2013-10-31.
  17. ^ "JavaScript 2 and the Open Web". 2007-11-20. Retrieved 2014-01-20.
  18. ^ "ECMAScript Harmony". Mail.mozilla.org. Retrieved 2013-10-31.
  19. ^ "A Major Milestone in JavaScript Standardization - JScript Blog - Site Home - MSDN Blogs". Blogs.msdn.com. 2009-04-09. Retrieved 2013-10-31.
  20. ^ "Ecma International finalises major revision of ECMAScript". Ecma International. 2009-04-09. Retrieved 2009-05-22.
  21. ^ "Ecma latest news". Ecma-international.org. Retrieved 2013-10-31.
  22. ^ John Resig. "John Resig - ECMAScript Harmony". Ejohn.org. Retrieved 2013-10-31.
  23. ^ harmony:specification_drafts [ES Wiki]. Wiki.ecmascript.org. Retrieved on 2013-10-23.
  24. ^ [5]. Twitter. Retrieved on 2014-07-31.
  25. ^ "Welcome to TypeScript". Typescriptlang.org. Retrieved 2013-10-31.
  26. ^ "JavaScript - JScript - ECMAScript version history". Webmasterworld.com. Retrieved 2009-12-17.
  27. ^ "Version Information (JScript)". Msdn.microsoft.com. Retrieved 2009-12-17.
  28. ^ "Introducing JScript .NET". Microsoft.com. Retrieved 2010-01-12.
  29. ^ "ECMAScript Language – test262". Test262.ecmascript.org. Retrieved 2013-10-31.
ISO Standard
Ecma Standards


Retrieved from "https://en.wikipedia.org/w/index.php?title=ECMAScript&oldid=619293362"