On Thu, Feb 7, 2008 at 8:38 AM, Karp, Alan H <[email protected]> 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
_______________________________________________
e-lang mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/e-lang
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.