thanks for the answer, bob. Bob Showalter wrote: > There's nothing that says the file Foo/Bar/Constants.pm must have a "package > Foo::Bar::Constants" declaration.
true, and i've realized that. i come from a python background and by contrast, in python, filename and directory name dictate the package/namespace. > But I think you'll find this kind of thing goes against the spirit of how > modules work. indeed. i still want to name my package Foo::Bar::Constants. the 'X' (or let's name it 'tmp') is just a temporary prefix to help ease my weary typing hands. in python i can do something like this: import Foo.Bar.Constants print Foo.Bar.Constants.alice tmp = Foo.Bar.Constants print tmp.alice tmp2 = tmp print tmp2.alice the three 'print' statements print the same thing. i had thought that in perl we can do some aliasing with the symbol table (the * and \* stuffs)? this is one beast i have yet to understand. > Another approach might be to stuff those values into a hash and export just > the hash: hm, i don't think i like this approach. i don't want to hashify everything. -- dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
