On Jul 9, 2008, at 10:05 PM, Allen Wirfs-Brock wrote:
I’m also confused about this. My understanding was, other than
perhaps some of the details I was specifically looking for feedback
on, that what I specified was generally what ES4 was planning on
doing.
See my reply to Mark citing
http://wiki.ecmascript.org/doku.php?
id=meetings:minutes_mar_27_2008#technical_notes
"[W]hat ES4 was planning on doing" needs to be qualified with "under
the default version" of JS, or under opt-in versioning. Again since
default versions get differing function statement semantics depending
on browser, unless all browsers can afford to break existing browser-
specific content, the change to unify on proposed ES4 semantics may
need to be under opt-in version selection only.
If some browsers implemented in a way that happens to work for most
browser-specific content (it's hard to be sure), then perhaps those
implementations could just make the change. But for cross-browser
portability, web scripts would want to select the explicit version
that guarantees the new semantics (and syntax, for that matter) in
all browsers that support that version.
/be
_______________________________________________
Es4-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es4-discuss
