[e-lang] Fwd: [Caja] An experiment and some questions

[ihab.awad at gmail.com]

On Thu, Feb 7, 2008 at 8:38 AM, Karp, Alan H <alan.karp at hp.com> wrote:

> Is there any reason that the importing module can't make its scope
> available to the imported module if it wants to?


If it wants to, it can, sure. I guess there are 2 aspects to this:

1. Does the imported module have unfettered read access to everything in my
scope? In other words, does it inherit all capabilities that exist in my
scope?

2. Does the imported module have unfettered write access to my scope? In
other words, am I doing the equivalent of "from <foo> import *"?

In any case, making things explicit is always better imho. Does that make
sense?

Ihab

-- 
Ihab A.B. Awad, Palo Alto, CA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/e-lang/attachments/20080207/24930635/attachment.html