According to Ed Peschko: > >> Suppose you want to export a certain module everywhere, so it is > >> visible to each scope. (Dumper, strict, whatever). What would really > >> be necessary is having these 'use' statements attached to each 'package' > >> statement. > > > >Then you're SURE to break things, because all of those modules would > >end up imported into every single module, certainly including some > >that just don't want things imported into them, thank you very much. > > Ok, then I guess the best way around this (assuming that you want to enforce > control on something like 'use strict') is to have the option to put PERL5OPT > in the executable, and then have a 'Common' module which contains horrifically > obscure code to insert the 'use' statements into each and every right > namespace. "Right" namespace? How do you know which ones are "right", even in theory? > (Although, to tell you the truth my experience a pragma to insert > all of this stuff into every namespace wouldn't break much) I think you need to experiment a bit more. There's a reason for @EXPORT_OK. -- Chip Salzenberg - a.k.a. - <chip@valinux.com> "I am the Lemon Zester of Destruction!" //MST3K