ES Native Mode proposal

Michaël Rouges michael.rouges at gmail.com
Wed Sep 25 12:31:26 PDT 2013


Hum ... in this proposal case, I don't think we should talk about a
real new version
of the language ...

Rather, I see it as a JavaScript sandbox that, internally, should not
require major developments, I believe

Michaël Rouges - https://github.com/Lcfvs - @Lcfvs


2013/9/25 Rick Waldron <waldron.rick at gmail.com>

>
>
>
> On Wed, Sep 25, 2013 at 11:41 AM, Michaël Rouges <michael.rouges at gmail.com
> > wrote:
>
>> Hi all,
>>
>> Given the number of scripts from various sources that may be contained in
>> a web page, there may be prototyping conflicts.
>>
>> To solve this, heavy techniques are often used, such as iframes, to execute
>> code in peace.
>>
>> I'm often thinking it might be much easier to tell the browser to have a
>> native to a given context, incidentally, to the functions from this
>> context & nested, regarding on the last relative scope with this
>> instruction.
>>
>> What I suggest, therefore it is a complementary mode to `'use strict'`...
>> the `'use native'`.
>>
>
> This list has been around the new pragma block several times and in the
> end the following (or something similar) holds: adding a new pragma will
> effectively creates a new "version" of the language and that's not going to
> happen any time soon.
>
> Rick
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130925/5818ccdc/attachment-0001.html>


More information about the es-discuss mailing list