Le 24/12/2012 23:37, Brandon Benvie a écrit :
To clarify: are you asking if an arbitrary object is a valid global
object when using a custom loader? If not, then I have a lot of code
to rewrite.
What I'm asking is:
"is the global in the loader the initial or the dynamic value of the
"global" option?"
If dynamic value, my snippet will log "37".
If initial value, my snippet will throw a ReferenceError originating
from the eval-ed script (because there is no "a" global in the initial
global)
I assume any object can be used as a global in a loader. I see no
restriction in the proposal.
David
On Mon, Dec 24, 2012 at 5:34 PM, David Bruant <bruan...@gmail.com
<mailto:bruan...@gmail.com>> wrote:
Hi,
I've reading the loader API [1] and I was wondering if it was
possible to dynamically change the global. I think it is by doing
the following, but tell me if I'm wrong:
const options = {
global : {
changeGlobal: function(g){
options.global = g;
}
}
}
var l = new Loader(Loader, options);
l.eval('changeGlobal({a:37}); console.log(a);');
In other words, in the global in the loader the initial or the
dynamic value of the "global" option?
If it was the dynamic value, I think it would help a lot in the
document.open situation [2]
David
[1]
http://wiki.ecmascript.org/doku.php?id=harmony:module_loaders#loader_api
[2] http://lists.w3.org/Archives/Public/www-dom/2012OctDec/0166.html
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org <mailto:es-discuss@mozilla.org>
https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
