B.3.1 The __proto__ pseudo property

Andrea Giammarchi andrea.giammarchi at gmail.com
Tue Apr 23 18:22:48 PDT 2013

then is more Ha, ha, ha.  Lulz, I told you, lulz! this one?

'__proto__' in {__proto__:null,"__proto__":null}

On Tue, Apr 23, 2013 at 5:34 PM, Jeff Walden <jwalden+es at mit.edu> wrote:

> On 04/21/2013 03:27 PM, Mark S. Miller wrote:
> > Warning: The following is a sickening idea. I would really hate to see
> us do it. But I feel obliged to post it as it may in fact be the right
> thing to do.
> >
> > This suggests that, in JS as well, the "__proto__" in {....,
> "__proto__": ...., ....} not be treated as a special case. Quoting it turns
> off the special treatment.
> For the lulz, what do these print in engines?
>   print(eval('[{"__proto__":  17}]')[0].hasOwnProperty("__proto__"));
>   print(eval('[{"__proto__":0x17}]')[0].hasOwnProperty("__proto__"));
> And considering what motivated real-world engine behaviors here, what
> constraints might possibly SunSpider imply?  (Conceivably none, to be sure,
> although I have my doubts a strstr could be eaten here.  Or maybe just
> another mode for the parser.  Ha, ha, ha.  Lulz, I told you, lulz!)
> Jeff
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130423/d1719698/attachment.html>

More information about the es-discuss mailing list