Comment #42 on issue 235 by erik.corry: Support the Javascript E4X extension http://code.google.com/p/v8/issues/detail?id=235
Before people get too excited about donating money to get E4X in V8 I should perhaps point out that there are at least three issues here:
1) Getting E4X into V8. This is difficult because it would have to be a very clean patch, that does not inconvenience those V8 programmers who don't use E4X (ie Google).
2) Getting E4X into Chromium or Google Chrome. This is even more difficult because we don't normally add things to the JavaScript implementation that are not part of the ECMAScript standards. We have been known to make exceptions in order to be Safari-compatible, but Safari doesn't support E4X so that doesn't apply in this case. This means that even if V8 had E4X support it would almost certainly be disabled in Google Chrome.
3) Getting E4X into the official version of node.js. This is of course up to Ryan, but last I checked he is no fan of E4X, preferring JSON. If he rejects it you can still put it in your own fork of course, and this applies to Chromium too.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
