Comment #84 on issue 235 by spl...@gmail.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
For anyone still watching this bug, you may want to know that E4X has been
dropped from Firefox, too. https://developer.mozilla.org/en-US/docs/E4X
"Warning:
Comment #83 on issue 235 by yang...@chromium.org: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Since E4X is not part of the ECMA-262 specification, it's not relevant
whether it's a standard by itself.
V8 is open source, so if you feel very strongly
Comment #82 on issue 235 by por...@gmail.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Ant, Maven, Eclipse, Flash Builder, Chrome, Visual Studio, etc etc... all
rely on XML; and, I'm pretty sure JSON won't be replacing XHTML anytime
soon, do yo
Comment #81 on issue 235 by vance.fe...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
waa. i want my xml!
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
Comment #80 on issue 235 by bret...@gmail.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
And "XML is still out there" is quite an understatement at that---It is
increasing in use on the web for document-centric data, as projects like
TEI are fin
Comment #79 on issue 235 by bartvand...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Thanks for the status update. While the result is not what I've personally
hoped for, at least your stance and motivations are clear, even somewhat
agre
Updates:
Status: WorkingAsIntended
Comment #78 on issue 235 by l...@chromium.org: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
There is still no plan to implement E4X in V8. Nothing has changed this in
the time the feature request has been op
Comment #77 on issue 235 by therealb...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
E4X (ECMA-357) is a dead-end standard. The future is an "E5X" that desugars
to ES5 strict or ES6 (E4X does not desugar due to filtering predicates,
whic
Comment #76 on issue 235 by nunojobp...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@bart: This is the related discussion in the node mailing list:
http://nodejs.markmail.org/search/?q=e4x#query:e4x+page:1+mid:tqwtyxl4uadyuxq6+state:results
Comment #75 on issue 235 by bartvand...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I'm thinking about filing a seperate bug report stating the V8 Feature
Request process is malfunctioning. Like stated in comment #71, whether this
featu
Comment #74 on issue 235 by musaadha...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Last year, there was the speed argument. But now Firefox has demonstrated
that it can interpret Javascript at comparable speeds even with all
the "encum
Comment #73 on issue 235 by musaadha...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Lats year, there was the speed argument. But now Firefox has demonstrated
that it can interpret Javascript at comparable speeds even with all
the "encum
Comment #72 on issue 235 by nunojobp...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
https://img.skitch.com/20110809-e7rye62w3qcr3enyhk68bheyur.jpg
Attachments:
Issues - v8 - V8 JavaScript Engine - Google Project Hosting.jpg 72.2 K
Comment #71 on issue 235 by nunojobp...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I would like someone to either mark this an wontfix or give it a priority
and accept it.
It doesn't help not knowing. This is the oldest not accepted FR
Comment #70 on issue 235 by bartvand...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Speaking from extensive experience with E4X in AS3 i say it works pretty
awesomely, way better then any other way. It totaly fits javascript,
compare DO
Comment #69 on issue 235 by track...@gmail.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
I know I chimed in fairly early on this... to me, the biggest use with be
with node in order to interact with existing web services, and wsdl based
systems
Comment #68 on issue 235 by nithril: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
JSON is not an alternative to XML when we talk about documents with a
grammar (schema) stored inside an XML repository.
--
v8-dev mailing list
v8-dev@googlegroups.com
ht
Comment #67 on issue 235 by mar...@laverdet.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Someone pointed me to this thread and since it seems like this venue has
pretty much lost all sense of bearing to v8 and turned into a discussion on
the f
Comment #66 on issue 235 by iamanthr...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Seems like there's plenty of NodeJS users who want to implement E4X
http://groups.google.com/group/nodejs/browse_thread/thread/713067d9d9db64e7/2260a8fa3513
Comment #65 on issue 235 by ludicco@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Speaking about outputting HMLT/XML here and my example at Stackoverflow
website:
http://stackoverflow.com/questions/5057087/e4x-with-nodejs
yes how eas
Comment #64 on issue 235 by nstansb...@redbacksystems.com: Support the
Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@prettyrobots.com
XML was a fad and EX4 spoke to that fad
An inept attempt at petty politics. XML as well as general DOM based data
is here to
Comment #63 on issue 235 by iamanthr...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@Brad
Firefox used a switch to enable it in the script tag, not sure if it still
requires it, but It think it does. There's no reason the same switch to
Comment #62 on issue 235 by bradley@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I have a few concerns that I would like to post about E4X.
1. It would require adding a XML system to the Javascript if you use
embedded v8 (and a large
Comment #61 on issue 235 by bcop...@gmail.com: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
E4X would be a sweet addition to Chrome and V8... hope someone takes a look
at it, as implementing the spec can't be that hard for Google's brilliant
engine
Comment #60 on issue 235 by downchuck: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
In case it was missed, E4X is well represented:
http://en.wikipedia.org/wiki/E4X
Boris recently pointed out a reasonable use case:
http://lists.w3.org/Archives/Public/pub
Comment #59 on issue 235 by iamanthropic: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
If you need E4X for business purposes as you desire the ability to use
Chrome to replace IE in your intranet but desire E4X before consideration,
please add your
Comment #58 on issue 235 by rff.rff: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
yet another advantage of e4x support: porting extensions from firefox would
be easier
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-de
Comment #57 on issue 235 by mconstable: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I suspect those who dislike the very idea of E4X have never used it. Server
side example...
var header = "My Page",
stuff = "I love e4x"
var body =
{header}
Comment #56 on issue 235 by musaadhaider: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
@renat.zubairov
Exactly!
@a...@prettyrobots.com
Millions don't want the latest shinny bobble that catches the eye of
attention deficit developer.
Does being the
Comment #55 on issue 235 by renat.zubairov: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
BTW just noticed, that's the most "starrred" feature, is that not a reason
for it?
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/grou
Comment #54 on issue 235 by renat.zubairov: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
I would agree with iamanthropic. XML sucks but it's there and we need a
support for it.
Right now we are evaluating usage of JavaScript in the data integration
Comment #53 on issue 235 by iamanthropic: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
@brettz9
It's not unreasonable to presume he/she was/is trolling as the negative
posts are their only ones on Google Code. It's probably not their fault
they don
Comment #52 on issue 235 by brettz9: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Firstly, 5 million speakers is not a few. Secondly, my point is not that
Esperanto is necessarily an ideal language (though it may be--as with any
standard, consensus mu
Comment #51 on issue 235 by tracker1: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I'm with pawel on this one... Most of the arguments against its'
integration could be made against inline regular expressions as a whole...
It's a feature that many (
Comment #50 on issue 235 by pawel.knapik: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
XML was a fad and EX4 spoke to that fad.
I hate XML. I hate being forced to deal with it instead of, say, JSON. But
it's out there and, sadly, it doesn't seem t
Comment #49 on issue 235 by a...@prettyrobots.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Esperanto? You do realize you're not making the point you're trying to make
with that analogy?
That's a good analogy, though. EX4 is the Esperanto of Ja
Comment #48 on issue 235 by brettz9: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Trolling in issue trackers? E4X is used all over the codebase of the
chatting application, sameplace/xmpp4moz, among other places apparently,
given the popularity of thi
Comment #47 on issue 235 by a...@prettyrobots.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Millions don't want the latest shinny bobble that catches the eye of
attention deficit developer. E4X is a silly extension. You can use one of
the many
Comment #46 on issue 235 by iamanthropic: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
@agnislav
Erik is well aware of the status of e4x being an extension he just keeps
leaving that out when he posts and has to keep correcting writing further
post
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
Comment #44 on issue 235 by agnislav: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Dear Eric,
Firstly I want to correct your statement about "not part of ECMAScript
standards". E4X is standardized as ECMAScript extension. It means "E4X is a
standard
Comment #43 on issue 235 by musaadhaider: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
"This is of course up to Ryan, but last I checked he is no fan of E4X,
preferring JSON."
So its all up to one guy then. His personal preferences trump what milli
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. Thi
Comment #41 on issue 235 by agnislav: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
e4x +1.
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
Comment #40 on issue 235 by trelliscorp: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
To anyone who has worked with E4X (or LINQ, Microsoft's implementation), it
seems unconscionable not to include it in every browser. As musaadhaider
pointed out,
Comment #39 on issue 235 by musaadhaider: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
You are right Matthew. E4X has been available since 2006 if I remember
correctly. Unfortunately, web browsers developers are too busy making
Javascript run 1ms f
Comment #38 on issue 235 by matthewAdavid: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
E4X has been part of Flash ActionScript for several years. It is really
great to develop to. It really is great.
--
v8-dev mailing list
v8-dev@googlegroups.com
Comment #36 on issue 235 by brettz9: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Sorry, for my ignorance, but is it possible the code could be developed so
as to be able to offer to work with Safari too (if they are open to it)?
In any case, I set up
Comment #35 on issue 235 by mconstable: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
The donation idea is not too bad, I'd also contribute $100, that's $200 so
far. Perhaps a non-Google dev could figure out a way to add E4X support as
some kind of V8
Comment #34 on issue 235 by 1nv151b13.b0b: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
although a string implementation wouldn't do enough, resorting to strings
would likely encourage other people to work on a in-client verson, would
only need to
Comment #33 on issue 235 by brettz9: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
As far as donations, maybe try pledgie.com.
Btw, despite my seeing the commenters' points about advantages for SSJS, my
main interest is to see E4X on the client. There i
Comment #32 on issue 235 by iamanthropic: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Is there any way to donate toward development of e4x?
Could someone give a rough quote and expected project timeline that people
could donate towards or something
Comment #31 on issue 235 by mconstable: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I can't believe E4X is not a part of already or under serious consideration
for V8. As erik.corry said in #19, if anyone else can create a clean
acceptable patchset t
Comment #30 on issue 235 by 1nv151b13.b0b: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
this has the most stars (48), the next highest is 29.
i would think that SOMEONE is trying to add it in.
--
v8-dev mailing list
v8-dev@googlegroups.com
http://grou
Comment #29 on issue 235 by 1nv151b13.b0b: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
we NEED E4X!!!
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
Comment #28 on issue 235 by ryan.gahl: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
In the mean-time, Jaxer (jaxer.org) is based on spidermonkey, and could be
used in a
nice little "nginx > node.js > jaxer" configuration in order to get the
awesomenes
Comment #27 on issue 235 by stackjr: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
SVG is XML, and javascript e4x would be the best way to handle it in HTML5
apps and websites. Hopefully, U
guys can find a way to get e4x into V8.
--
v8-dev mailing li
Comment #26 on issue 235 by musaadhaider: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Well I am not trying to rant here as its Google's decision in which
direction they
want to take their web browser and I respect that. But speaking what I
really
Comment #25 on issue 235 by trapni: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
vote plus 1 for E4X
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue
Comment #24 on issue 235 by erik.corry: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@rich.aloha Yes, I misspoke. E4X is a standard. However, it is not a part
of
standard ECMAScript.
--
You received this message because you are listed in the owner
o
Comment #23 on issue 235 by rich.al...@gmail.com: Support the Javascript
E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@erik.corry
"E4X is standardized by Ecma International in the ECMA-357 standard. The
first
edition was published in June 2004, the second edition in Dece
Comment #22 on issue 235 by tracker1: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
While I agree that E4X isn't a hugely needed technology for use within the
browse
(not that it isn't useful), I do feel it is an essential component to use
of the V8
e
Comment #21 on issue 235 by tracker1: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
http://www.ecma-international.org/publications/standards/Ecma-357.htm
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
Comment #20 on issue 235 by tracker1: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
http://www.ecma-international.org/publications/standards/Ecma-357.htm
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
Comment #19 on issue 235 by erik.corry: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
The issue here is that e4x isn't in a standard and it isn't on the way to a
standard
and it isn't a de facto standard in browsers (esp. Safari). As such it is
no use
Comment #18 on issue 235 by canerbalci: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
i dont think e4x will be the next SVG. there are very good libraries for
using
javascript on the server side(ie. nodejs) and e4x could be a killer feature
of v8 even
Comment #17 on issue 235 by jbsurveyer: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
There is a good posting on the issue of E4X support at :
http://www.theopensourcery.com/keepopen/?p=2157
Unfortunately E4X is at a tipping point now that all the browse
Comment #16 on issue 235 by jacobusreyneke: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
@cainus: I was having a bad day ;-)
It just sometimes gets under my skin to think about the amount of time
developers
waist because good technologies are not su
Comment #15 on issue 235 by cainus: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@jacobsreyneke: You should demand your money back while you're at it!
--
You received this message because you are listed in the owner
or CC fields of this issue, or becaus
Comment #14 on issue 235 by brickysam26: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
For those of you interested in E4X for its simplicity and not because of
the syntax
shortcuts or native data types. You can checkout xbe4x
[http://code.google.com/
Comment #13 on issue 235 by jacobusreyneke: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
It is simply scary that E4X is still not supported. We waited 10 years to
get the big
boys to realize that SVG is here to stay. Same for E4X - It's here to stay.
Comment #12 on issue 235 by llabret: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
Any chances on a partial implementation? I'd love to be able to use 'for
each'.
--
You received this message because you are listed in the owner
or CC fields of this iss
Comment #11 on issue 235 by musaadhaider: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
E4X to a lot of developers is a very important feature. I and my team
design intranet
applications for my company and we are not going to give up E4X even if we
ha
Comment #10 on issue 235 by ro...@robinwinslow.co.uk: Support the
Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I wish we could get a little more than that one line of input from a Google
developer.
E4X would be great.
--
You received this message because you are
Comment #9 on issue 235 by spullara: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
@XMLArchitect The part of E4X support that is interesting is the native XML
datatypes
and xpath support.
--
You received this message because you are listed in the owner
Comment #8 on issue 235 by XMLArchitect: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Just found the following: http://libxmljs.squishtech.com/
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #7 on issue 235 by pawel.knapik: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
If you just want to format data in a structured form, JSON may be an
alternative, but
that's it. It is not an alternative when you need to work with XML
documents
In a way I agree (despite the old gmail name :) in the same way that
I prefer Erlang, Python, and Javascript over Java. I do think XML is
here to stay though as the use cases do not completely overlap JSON
use cases. AFAIK XML is designed to convey meaning in a structured
way vs JSON, which is d
Comment #6 on issue 235 by erik.corry: Support the Javascript E4X extension
http://code.google.com/p/v8/issues/detail?id=235
I think the alternative solution that works is json.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred t
Comment #5 on issue 235 by XMLArchitect: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Yeah, E4X support is necessary IMHO. Flip-side is it's open source, so up
to us to
implement if those more versed in V8 that are at Google don't feel the need.
Thoug
Comment #4 on issue 235 by ulr...@dots.de: Support the Javascript E4X
extension
http://code.google.com/p/v8/issues/detail?id=235
Many people using JS for server side are looking for E4X. Currently there
is no
alternative for Spidermonkey even though V8 is the fastest engine today and
has a
81 matches
Mail list logo
