I'd prefer the heading be Scripts and LegacyScripts. Just so happens that the module features are only available in Scripts.
- Matthew Robb On Wed, Sep 10, 2014 at 2:28 PM, Matthew Robb <matthewwr...@gmail.com> wrote: > I don't see how this is not forking: > http://people.mozilla.org/~jorendorff/es6-draft.html#sec-ecmascript-language-scripts-and-modules > > There are now two distinctly different models and yes they both work in > the same VM simultaneously but that's not what authors would care about. > Personally I want to be able to know at all times that a file I am looking > at is a script or a module without using tools to assume one or the other. > > The problem with the link above is that A) It associates this new > local-global-scoping/implicit-strict-mode with modules rather than > generically and B) Neither mode is specified as of higher importance which > results in exactly a forked paradigm. > > > - Matthew Robb > > On Wed, Sep 10, 2014 at 2:15 PM, Brendan Eich <bren...@mozilla.org> wrote: > >> Matthew Robb wrote: >> >>> But if the goal is for everything going forward to use the scope >>> environment characteristics of modules (strict-mode and local-global) then >>> why not specify that and move the old model to a legacy mode. >>> >> >> What "old model"? There's one spec. We are not forking specs. Engines are >> not forking into two VMs. >> >> /be >> > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
