Btw, another question that has bugged me lately: with "1JS", what
happens when I do a sloppy-mode direct eval on a program string
containing a module declaration? In global scope? In local scope?
It's a good question, and one I've thought about some. This could
use some whiteboard time -- let's discuss next week when you're in town.
Would this be a good time to mention my previous questions?
modules: import hiding, and usage patterns
https://mail.mozilla.org/pipermail/es-discuss/2012-February/020420.html
supporting ES upgrading with a programming pattern repo?
https://mail.mozilla.org/pipermail/es-discuss/2011-November/018240.html
Previously, I've been told that the time isn't ripe for such discussions.
Like some others, I'm concerned about the (relatively) low profile
of modules in discussions here.
There are groups who like the static aspects, groups who think the
dynamic aspects will cover the remaining use cases, and groups
who wonder whether established use patterns will have to fall
back on loaders for so many cases that the static aspects might
be defeated. Or how the static aspects are going to be integrated
in a dynamic web software delivery context.
Just as with classes, even the best ideas need to be confronted
with practice (of which home-brew modules in JS have had a lot).
Claus
PS. module M from URL;
import item from M;
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
