Putting `global` reference in specs

[Andrea Giammarchi]

at this point you mean it will never be introduced, not even as alias in
ES7 or ES8, do I understand correctly?

Best Regards

On Sat, Apr 18, 2015 at 5:17 AM, Brendan Eich <brendan at mozilla.org> wrote:

> We cannot introduce a global property named `global` at this point.
>
> I don't think everyone replying lately has read the whole thread carefully
> :-|.
>
> /be
>
> Andrea Giammarchi wrote:
>
>> Sure workers too, but it doesn't in server side and it doesn't mean
>> anything meaningful for all developers coming from other languages. `self`
>> is a misleading word and in ES6 specs we have mentioned global object and
>> never a single word for the `self` keyword, or its meaning.
>>
>> `global` does not need that kind of explanation you put down for
>> historical purpose, `global` is well known meaning for everyone in JS
>> world, including members in this ML that would refer to the global scope,
>> and the global object, regardless they mean sometimes `realm` ... or isn't
>> it?
>>
>> On Fri, Apr 17, 2015 at 10:38 PM, Brendan Eich <brendan at mozilla.org
>> <mailto:brendan at mozilla.org>> wrote:
>>
>>     The principle extends just fine to workers, and has.
>>
>>     /be
>>
>>
>>     Andrea Giammarchi wrote:
>>
>>         And that's indeed the only place on Web world where `self`
>>         makes sense:
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150418/f019f603/attachment-0001.html>