On 27/10/10 21:38, Brendan Eich wrote:
Is there consensus that this is defacto standard behavior that is needed for
interoperability among browsers and that it should be incorporated into Harmony?
I suspect this is a de-facto standard we should codify in Harmony. Thanks for
bringing it up.
How much of de-facto standards are going to be codified? What about
things which aren't entirely interoperability implemented, but the basic
premise is an absolute requirement for web compatibility (e.g., the
recent thread on function hoisting). What about things which are needed
for web compatibility, interoperability implemented, but disallowed in
ES5/Strict (e.g., Function.arguments, Function.caller, octal escapes
(which are defined differently to all impls as raised before ES5 was
finalized), etc.)?
I'd very much like to get to a point where you can implement something
web compatible from the spec, which would mean defining things some
don't like, and changing other definitions that people don't like
either… At the moment, it's impossible to implement a fully compliant
ES5 implementation without sacrificing web compatibility.
--
Geoffrey Sneddon — Opera Software
<http://gsnedders.com>
<http://opera.com>
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
