Sorry, I mistakenly interpreted E4X as EcmaScript4. Any time I see E and 4 together, it clicks as ES4 for me.
Yes, handling XML natively in JS would be nice for those who are not using JSON. On Mon, Mar 30, 2009 at 4:01 AM, Mike Douglas <[email protected]> wrote: > > On Mar 29, 8:18 am, Mikhail Naganov <[email protected]> wrote: >> Well, if you're really interesting in using ES4 right now, you can use >> Mascara translator:http://blog.ecmascript4.com/ > > I don't think E4X is part of the Harmony spec. > > E4X is a standardized extension to ECMA-262 for handling xml. Its > advantage over a DOM interface is that XML data becomes a primitive, > allowing for a much simpler API that resembles objects. At the same > time, it's nicer than what an object mapping interface could provide, > because of some differences in Javascript and XML (object properties > aren't ordered, while XML is), and the nice XPath-like path navigation > syntax. The spec is available at > http://www.ecma-international.org/publications/standards/Ecma-357.htm. > > IMHO, this is a pretty good spec that's suffered some bad > implementations. Integrating this into v8 would not only have positive > implications on the browser-side, but would really strengthen v8's > case as a general purpose, embeddable scripting language. > > > --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
