Re: Composition of Uncoordinated Working Sets of Modules

2010-06-07 Thread Sam Tobin-Hochstadt
On Sun, Jun 6, 2010 at 2:00 PM, Kris Kowal kris.ko...@cixar.com wrote: Supposing that aQuery and bQuery are implemented by independent uncoordinated authors. aQuery.js    module $ {    } bQuery.js    module $ {    } If my interpretation is correct, these cannot be combined in a

Re: Composition of Uncoordinated Working Sets of Modules

2010-06-07 Thread Kris Kowal
On Mon, Jun 7, 2010 at 8:37 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: On Sun, Jun 6, 2010 at 2:00 PM, Kris Kowal kris.ko...@cixar.com wrote: ... Most of this is good clarification, particularly that load interacts with the exports of the foreign script's implied, anonymous module scope.

Re: Composition of Uncoordinated Working Sets of Modules

2010-06-07 Thread Erik Arvidsson
On Mon, Jun 7, 2010 at 10:35, Kris Kowal kris.ko...@cixar.com wrote: Another thing that Ihab clarified which merits a full section on the wiki is the dynamic scoping of lexical module names. This is a common misconception. Simple modules is using static lexical scoping, not dynamic scoping.

Re: Composition of Uncoordinated Working Sets of Modules

2010-06-07 Thread David Herman
It would be good for this to be expressed in one of the examples, and for it to be clarified in the description of semantics that every script is also an anonymous module from which the exports are only accessible through the lexical scope shadowing (I assume) and by being bound to a module

Re: Composition of Uncoordinated Working Sets of Modules

2010-06-07 Thread Kris Kowal
On Mon, Jun 7, 2010 at 12:10 PM, Erik Arvidsson erik.arvids...@gmail.com wrote: On Mon, Jun 7, 2010 at 10:35, Kris Kowal kris.ko...@cixar.com wrote: Another thing that Ihab clarified which merits a full section on the wiki is the dynamic scoping of lexical module names. This is a common