Standard builtins' prototypes and toString

[Mark Miller]

I am happy with #b as well, though I prefer #c. I also agree with C.
Scott's interpretation of #c, to mean, appropriate degenerate value, which
is generally the zero value, but is plausibly NaN for Date.

Whichever experiment Nightly tries first with a positive outcome, I expect
that's what we'll do, since the difference between #b and #c is not large
enough to be worth waiting for a second experiment.




On Tue, Jun 17, 2014 at 8:37 AM, C. Scott Ananian <ecmascript at cscott.net>
wrote:

> On Tue, Jun 17, 2014 at 11:33 AM, Allen Wirfs-Brock
> <allen at wirfs-brock.com> wrote:
> > I'm not sure who introduced the idea that the Date.prototype should have
> a
> > "zero value", but that is inconsistent with ES3&5 where the TimeValue of
> > Date.prototype is NaN:
> > http://www.ecma-international.org/ecma-262/5.1/#sec-15.9.5 If we went
> the
> > (c) route it should presumably be modified to use NaN and not 0.
>
> Sorry, I was using quotes around "zero value" on purpose to mean, "the
> appropriate value for the given type" (which is not actually 0).  Date
> should be NaN, boolean should be false, etc.  I hope most of those
> reading understood this.
>   --scott
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>



-- 
Text by me above is hereby placed in the public domain

  Cheers,
  --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140617/9c29af8e/attachment.html>