Support for ECMA-357 E4X syntax about traceur-compiler HOT 3 CLOSED

From [email protected] on May 16, 2011 17:43:06
FYI, E4X is dead. The spec is not even compatible with ES5 and no one has shown any interest in updating it to work with ES5.

That said, I do think that if someone submitted patches to add it Traceur and it was under a flag we would accept it.

from traceur-compiler.

From [email protected] on May 16, 2011 18:18:57
The agreement in TC39 was for Mozilla and Adobe to evolve an ECMA-357 (E4X) successor, I jokingly call it E5X, and evolve it from crazyland to have runtime semantics that can be implemented by proxies. The XML syntax is partly actually good and salvageable, better if done via a syntactic extension mechanism, but lacking that, still separable into an E4X spec.

This was all recorded in meeting notes, IIRC.

/be

from traceur-compiler.

From [email protected] on June 24, 2011 05:39:18
Facebook actually took the idea of E4X and modified their PHP runtime so that UI component can be easily constructed with XML, and manipulated as an Object instance.

For example:

// See http://codebeforethehorse.tumblr.com/post/3096387855/an-introduction-to-xhp
$blog_post =

$blog_post .setId('foo');
print $blog_post ->toString(); // so you get the HTML .

It's a great way to build and render UI consistently and I'd like to see this feature available in JS, too.

from traceur-compiler.