Talk:ECMAScript for XML

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)

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)

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)

This is untrue: "JSON is an object-oriented data notation similar to XML." and should be removed. JSON is in no way similiar to XML. JSON is not a data notation, it's the syntax for creating a new javascript object, according to that description of JSON Java would also fit the bill as an OO data notation similiar to XML.... XML is also not object oriented. I could go on and on about the differences. They are completely unrelated technologies. Soverby (talk) 17:25, 2 May 2009 (UTC)

I think there should be some mention of the problems with/controversy surrounding the spec. In particular Mozilla's decision not to submit an E4X test for Acid 3 is of relevance. See http://www.webstandards.org/2008/01/16/whats-the-best-test-for-acid3/#comment-59499 and http://shaver.off.net/diary/2008/03/27/the-missed-opportunity-of-acid-3/#comment-135680. TheCycoONE (talk) 18:14, 19 November 2009 (UTC)

Why deprecated

Something should be said in the article about why e4x has been deprecated. Teo8976 (talk) 19:50, 24 January 2016 (UTC)

Does E4X supported in NodeJS? — Preceding unsigned comment added by 95.161.141.5 (talk) 11:50, 7 December 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on ECMAScript for XML. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Added archive https://web.archive.org/20150602131200/http://www.ecma-international.org/publications/standards/Ecma-357.htm to http://www.ecma-international.org/publications/standards/Ecma-357.htm

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 13:27, 13 February 2016 (UTC)

ECMAScript-for-XML inspired XQuery?

XQuery is from 2007 and ECMAScript for XML from 2004... Are there a citation of the use (inspiration) at XQuery development?

External links modified

Hello fellow Wikipedians,

I have just modified 4 external links on ECMAScript for XML. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20120505042844/https://developer.mozilla.org/en/Firefox_10_for_developers to https://developer.mozilla.org/en/Firefox_10_for_developers
• Added archive https://web.archive.org/web/20090415002451/http://www.mozilla.org/js/spidermonkey/release-notes/JS_160.html to http://www.mozilla.org/js/spidermonkey/release-notes/JS_160.html
• Added archive https://web.archive.org/web/20081006212236/http://developer.mozilla.org/index.php?title=En%2FCore_JavaScript_1.5_Guide%2FProcessing_XML_with_E4X to https://developer.mozilla.org/index.php?title=En%2FCore_JavaScript_1.5_Guide%2FProcessing_XML_with_E4X
• Added archive https://web.archive.org/web/20080704203050/http://developer.yahoo.com/flash/articles/e4x-beginner-to-advanced.html to http://developer.yahoo.com/flash/articles/e4x-beginner-to-advanced.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 15:00, 15 September 2017 (UTC)