Hi Michael,
es-disc...@michael.ficarra.me writes:
Oh, sorry for the duplicate. It appears you guys were just recently
discussing this, though it failed to turn up in my searches.
The discussion only started on test262. If it's going to entice a spec
change, it's great to talk about it here.
(Sorry for the latency, but I only get internet access by tethering
here.)
bruan...@gmail.com writes:
Le 05/08/2013 17:08, Brendan Eich a écrit :
Michael Ficarra wrote:
specified that the global object's prototype chain must include
Object.prototype. I am sure there's plenty of code that
Hello,
es-disc...@michael.ficarra.me writes:
It has recently come to my attention that, though Object.prototype is in
the prototype chain of the global object in all interpreters I've ever
used, the [[Prototype]] of the global object is actually unspecified. My
question: was this property
Oh, sorry for the duplicate. It appears you guys were just recently
discussing this, though it failed to turn up in my searches. For what it's
worth, I would prefer for it to be specified that the global object's
prototype chain must include Object.prototype. I am sure there's plenty of
code that
Michael Ficarra wrote:
specified that the global object's prototype chain must include
Object.prototype. I am sure there's plenty of code that depends on that.
Yes, that's required.
/be
___
es-discuss mailing list
es-discuss@mozilla.org
Le 05/08/2013 17:08, Brendan Eich a écrit :
Michael Ficarra wrote:
specified that the global object's prototype chain must include
Object.prototype. I am sure there's plenty of code that depends on that.
Concern shared.
Yes, that's required.
Would it make sense to leave ECMAScript spec
David Bruant wrote:
Le 05/08/2013 17:08, Brendan Eich a écrit :
Michael Ficarra wrote:
specified that the global object's prototype chain must include
Object.prototype. I am sure there's plenty of code that depends on
that.
Concern shared.
Yes, that's required.
Would it make sense to leave
Le 05/08/2013 20:11, Brendan Eich a écrit :
David Bruant wrote:
Would it make sense to leave ECMAScript spec intact (global's
[[Prototype]] is implementation-dependent),
No, we want interop across, e.g., Node.js and browsers, on such
features as whether toString resolves as a global
It has recently come to my attention that, though Object.prototype is in
the prototype chain of the global object in all interpreters I've ever
used, the [[Prototype]] of the global object is actually unspecified. My
question: was this property intentionally unspecified to allow for
interpreters
9 matches
Mail list logo
