Yes, that's the idea.
Best,
Dave
On Apr 11, 2011, at 7:45 AM, Axel Rauschmayer wrote:
> My understanding is limited, but here it goes:
>
> You load modules in ES.next as follows:
>> module JSON = require('http://json.org/modules/json2.js');
>
>
> A custom module loader (loosely related to a Java class loader) can be used
> to intercept the module loading and return a different module. That is, you
> would configure a custom loader thusly:
>
> INSTEAD OF 'http://json.org/modules/json2.js' LOAD 'testmodules/json2.js'
>
> Corrections? Comments?
>
> Greetings,
>
> Axel
>
> On Apr 11, 2011, at 16:11 , Nathan Stott wrote:
>
>> Could you, or someone else, please explain what changing the semantics
>> of module URLs means? DI is an important issue and I'd like to
>> understand how it is intended to be achieved in the future module
>> system.
>
>>>> Module loaders do give you the ability to do dependency injection, though,
>>>> by changing the semantics of module URL's.
>
> --
> Dr. Axel Rauschmayer
>
> [email protected]
> twitter.com/rauschma
>
> home: rauschma.de
> blog: 2ality.com
>
>
>
> _______________________________________________
> es-discuss mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
