According to TOGoS: > Chip said: > > A Perl runtime won't have the necessary information > > to present [a unified namespace]. > > I'm not so sure about that. Most of the time, only one variable with > a name will be defined ($foo, @foo, or &foo, but not more than one).
That looks good in static analysis. But masking effects are serious enough that it's a bad idea, IMO. Consider: A working Perl/Python hybrid program would be broken by an upward-compable upgrade of the Perl part that makes a given name ambiguous, thus defeating the single-namespace view that used to work. Requiring explicit imports avoids this problem. > This reminds me just a little bit of what J# does to implement > accessors that can be used by other .NET programs. Do tell, please. -- Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]> "I don't really think it is a question of bright people and dumb people, but rather people who can see the game they're playing and those who can't." -- Joe Cosby
