I think that requiring a user load a parser to handle XML is perfectly fine. That's the state of the art in most programming languages.
On Mon, Jan 16, 2012 at 09:51, David Bruant <bruan...@gmail.com> wrote: > Le 16/01/2012 18:30, Nuno Job a écrit : >> Hi guys, >> >> I would like to make the case for better native XML support in ES5: >> >> This is the most commented open issue on V8: >> http://code.google.com/p/v8/issues/detail?id=235 >> Unfortunately people didn't agree on E4X and this makes the life of >> developers that have to use XML miserable. While XML is not a first >> class citizen in the web it is the preferred interchanged format in >> the enterprise. Developers don't choose to use XML over JSON, they >> sometimes have to use XML. A solution for this would be always better >> if in the language. > Have a look at quasis [1]. It provides what I'd consider to be a more > generic and safer solution to E4X. > You can send feedback to es-discuss@mozilla.org (es5-discuss is usually > reserved to ECMAScript 5 specifically, though most people who are in one > are certainly in both) > > David > > [1] http://wiki.ecmascript.org/doku.php?id=harmony:quasis > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
