On Scope And Prototype Security
andrea.giammarchi at gmail.com
Tue Mar 19 17:37:07 PDT 2013
FIY the Arguments class:
and to do not drop fireballs and run, me two years ago here:
(recently basically specced as Object.getPropertyDescriptor)
so maybe I am not always that crazy when I ask about things and propose
stuff ... just maybe.
Thanks for listening
On Tue, Mar 19, 2013 at 5:24 PM, Andrea Giammarchi <
andrea.giammarchi at gmail.com> wrote:
> inside my bloody own prototype! ==> my own closure/private scope
> On Tue, Mar 19, 2013 at 5:24 PM, Andrea Giammarchi <
> andrea.giammarchi at gmail.com> wrote:
>> "class" or prototype that does not exist out there, but it's defined inside
>> my bloody own prototype!
>> I have done here, apologies it took so long to provide the right example.
>> Now I'll wait 'till the day that would be possible, usually stuff I propose
>> takes 2 years before it goes out, it won't be the first time even here.
>> Best Regards
>> On Tue, Mar 19, 2013 at 5:21 PM, Brandon Benvie <bbenvie at mozilla.com>wrote:
>>> On 3/19/2013 5:17 PM, Andrea Giammarchi wrote:
>>> but [[Class]] of arguments is Arguments
>>> so this is exactly what I meant ... finally I found the perfect
>>> example: Arguments ... the class is unreachable, all instances can be
>>> manipulated, theoretically, behind the scene to throw, retrieve, or do,
>>> It's not that it's unreachable...it doesn't exist. The spec doesn't call
>>> for some hidden prototype object that properties can be on; it specifies an
>>> exotic object type with some different internal methods. Internal methods
>>> are not inherited prototypally.
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss