import script --> .esm

John Barton johnjbarton at google.com
Wed Sep 10 09:41:44 PDT 2014


On Wed, Sep 10, 2014 at 9:35 AM, Allen Wirfs-Brock <allen at wirfs-brock.com>
wrote:

>
> On Sep 10, 2014, at 9:28 AM, Matthew Robb wrote:
>
> As soon as the language decided it would have a differentiation for
> modules vs scripts then it seems only natural that it should also specify
> at least some generic means of entry into one mode or another. Then it's up
> to browsers or who ever to determine what external signifiers would trigger
> module instead of script. Or the language parsing logic could say that in
> the presence of module syntax it will always be treated as module. I don't
> know if that's feasible or not *shrug*
>
>
> Modules and scripts can not always be identified by inspection.  Consider:
>
> foo.js -------------------------------
> const answer = 42;
> ---------------------------------------
>
> The semantics of this are quite different depending upon whether foo.js is
> evaluated as a script or loaded as a module.
>

This case is clearly as script, as a module it has no effect right?  Isn't
the only ambiguous case would be explicit global manipulation, where we
could decide module is used and (most of the time ;-) win.

jjb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140910/afbb2e56/attachment.html>


More information about the es-discuss mailing list