Odd idea

Mark S. Miller erights at google.com
Sat May 17 19:37:25 PDT 2008

We've all been assuming that the current disconnect between JavaScript
version numbers and Ecmascript version numbers will continue. As I was
reading <http://wiki.ecmascript.org/doku.php?id=proposals:versioning&s=versioning>:

# For the application/javascript type, the version
# values already in use are 1.0, 1.1, 1.2, 1.3, 1.4,
# 1.5, 1.6, and 1.7 (note that these are not specified
# by RFC 4329 or by any ECMA specification).
# Implementations of ES4 MUST process content
# of type application/javascript with version equal
# to 2 the same as they would
# application/ecmascript with version equal to 4.

it occurred to me that it's not yet too late to end the madness. How
about if we align the next JavaScript version numbers with their
Ecmascript equivalents:

How about if the JavaScript version corresponding to ES4 is JavaScript
4? This also addresses the otherwise nasty issue of what the
JavaScript numbering should be for ES3.1. Let's call that JavaScript
3.1 as well.


More information about the Es4-discuss mailing list