Le 27/10/2011 12:08, Axel Rauschmayer a écrit :
+1. Where the spec is already almost pseudo-code, its readability
would improve if it was, in fact, pseudo-code. But would an extra
interpreter be needed or couldn’t one just implement the ES-262
constructs (execution contexts etc.) in an existing language (Python,
Rust, Scheme, Smalltalk, etc.)?
Why choosing a completely different language? Why not ECMAScript 5.1?
It will be one less language to learn as people who read the ES6 spec
are very likely to be familiar with ES5.1. I personnally wouldn't feel
comfortable reading a spec in any of the 4 languages you cited.
Or maybe define the couple of things that can't be fully implemented in
ES5.1 (proxies, private names) and use ES5.1 + these construct to define
ES6.
David
Might make the algorithm testing harder, though.
On Oct 27, 2011, at 8:19 , Allen Wirfs-Brock wrote:
I'm again considering creating a line-by-line translation of the ES6
spec algorithms into an executable evaluator of parse trees. this
would be a non-normative translation of the spec. that could be used
to test the algorithms.
--
Dr. Axel Rauschmayer
[email protected] <mailto:[email protected]>
home: rauschma.de <http://rauschma.de>
twitter: twitter.com/rauschma <http://twitter.com/rauschma>
blog: 2ality.com <http://2ality.com>
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
