Jump to content

Talk:ECMAScript for XML

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Daira Emma Hopwood (talk | contribs) at 03:39, 21 January 2009. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Removed the inappropriate category (Category:JavaScript dialects), as E4X is not a JavaScript dialect, but a language extension. --asqueella 195.146.72.90 15:49, 7 September 2005 (UTC)[reply]

Any chances it will still make it into the ECMAScript standard? Apparently it was dropped from "Harmony", what a pity. Is it being considered for future versions of Webkit, Opera, IE? —Preceding unsigned comment added by 87.162.59.111 (talk) 21:32, 12 November 2008 (UTC)[reply]

Any chances it will still make it into the ECMAScript standard?

None at all. For example:
We've often cited EIBTI [Explicit Is Better Than Implicit] in ES4 working group meetings. In general I daresay the TC39 committee is more in favor of avoiding implicit magic, especially conversions, now than ever (E4X, ECMA-357, is full of it, and it's a mess). --Brendan Eich
The contingent who were anti-ES4 would be even less likely to accept E4X as part of ES-Harmony. David-Sarah Hopwood (talk) 03:39, 21 January 2009 (UTC)[reply]