I almost omitted it, but one should never need to encounter or think about
sloppy code unless absolutely necessary. For my brain, adding the "use
strict"; makes this snippet of code much simpler.
On Fri, Apr 17, 2015 at 8:30 AM, Andreas Rossberg <rossb...@google.com>
wrote:
> On 17 April 2015 at 17:27, Mark S. Miller <erig...@google.com> wrote:
>
>> (1,eval)('"use strict"; this')
>>
>
> Is the 'use strict' relevant here? Seems overkill.
>
> /Andreas
>
>
>
>>
>> On Fri, Apr 17, 2015 at 8:23 AM, Andrea Giammarchi <
>> andrea.giammar...@gmail.com> wrote:
>>
>>> there's actually no way, officially, to reference what ES2015 call *the
>>> global object*, just pointless fragmentation between engines.
>>>
>>>
>>>
>>> On Fri, Apr 17, 2015 at 4:19 PM, Anne van Kesteren <ann...@annevk.nl>
>>> wrote:
>>>
>>>> On Fri, Apr 17, 2015 at 5:12 PM, Andrea Giammarchi
>>>> <andrea.giammar...@gmail.com> wrote:
>>>> > So I'd say we should not have `self` (if stays on global and Worker I
>>>> don't
>>>> > actually care) and add a `global` that nobody needs explanation to
>>>> > understand what it is in JavaScript
>>>>
>>>> Indeed, three ways to reference the global object is not nearly enough.
>>>>
>>>>
>>>> --
>>>> https://annevankesteren.nl/
>>>>
>>>
>>>
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss@mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>>>
>>
>>
>> --
>> Cheers,
>> --MarkM
>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss@mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>>
>
--
Cheers,
--MarkM
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
