ES4 draft: Namespace

Lars T Hansen lth at acm.org
Sat Mar 8 21:00:31 PST 2008


On 3/8/08, zwetan <zwetan at gmail.com> wrote:
> do I understand well that E4X will be removed from ES4 ???

It was never in ES4 to  begin with.

--lars

>  this is so wrong i can not even believe it...
>
>  try to parse XML in .NET/Java/PHP/whatever...
>  the ONLY elegant and straightforward way to do it is E4X imho
>
>  but ok let's stay on the standard and on the web,
>  look at how browsers parse XML without E4X
>
>  see why those projects exists
>  http://dev.abiss.gr/sarissa/
>  http://code.google.com/p/ajaxslt/
>
>  yeah that's the reality in browsers XML parsing sucks
>  because every browser does its own cooking...
>
>  so again, even if the E4X spec is buggy etc.
>  would it not be better to keep E4X and/or try to improve it within ES4 ?
>
>  I know this ML is focused on specs,
>  but I can really not understand why something as E4X
>  which is easy and powerfull to use for any dev would be removed
>
>
>  zwetan
>
> _______________________________________________
>  Es4-discuss mailing list
>  Es4-discuss at mozilla.org
>  https://mail.mozilla.org/listinfo/es4-discuss
>



More information about the Es4-discuss mailing list