Chip said: > ...the "appearance" of a unified namespace *is* > a unified namespace.
Yup. > A Perl runtime won't have the necessary information > to present one. 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). In these cases, the perl compiler would put 'foo' into the LCD namespace in addition to putting $foo @foo or &foo into the perl namespace. In cases where more than one is defined, it could default to scalar (probably what the hypothetical ruby/python programmer wanted), or let the perl programmer specify which one to use: add_module_accessor 'foo', $foo (or whatever). This reminds me just a little bit of what J# does to implement accessors that can be used by other .NET programs. It's a little clunky for the java programmer, but it makes the interface for everyone else much cleaner. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail