Comment #45 on issue 235 by iamanthropic: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
@Erik
is there perhaps a compromise that would allow e4x where it was to only
allow working with xml when defined as "new XML()" rather than xml in the
js source (as I know plenty of people don't like the idea of that)?
Essentially a built in method that allowed transforming of xml to a json
object that could be interrogated in the xm...@whatever e4x syntax that
would benefit interrogation of json data as well and keep everybody happy
while appearing to only miss one main part of the e4x standard. Really all
that would be needed would be the ability to search json e4x style with
addition of an attribute identifier or standard way to define object
attributes for searching with the @.
All developers really want is easy ways to process and scan/search data,
there must be a way to do so in a way advantageous and worthwhile to
Chrome, close enough to the standard of e4x for e4x lovers and not e4x
enough to be so useful to js that Ryan would be happy to put it in NodeJS?
Can't we all just get along? :)
It's 2010!
-Marcel
ps. Erik, thanks for taking the time to lay out the objections/barriers as
you see them, much appreciate your time and efforts on v8!
pss. We would all be flying around in personal spaceships by now if people
worked together and compromised more. Surely you know enough Chrome/Google
people to help convince them that there are a lot of people that would be
grateful if there was a compromise they could accept and allow us to pay
for development on?
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
