I don't know a lot about mod_perl so I did not have that in mind. Parallelism can be an issue when modifying package vars in different threads (as with anything else). But as there are different ways to import a module (e.g. use, require but especially do (and eval) which asker uses a lot) and there are also ways to reload a module at runtime (e.g. Module::Refresh) I thought it's better to leave a questionmark there rather than being absolute. Given also that there are other safer ways to achieve read-write effect. Personally I can't stand things like: $DBI::errstr, whereas $XYZ::DEBUG = 1 is tolerable.
What's your opinion? Can we rely on the state of a package's variables modified after loaded (not in mod_perl, threads)?
In reply to Re^5: How to import "global" variables into sub-scripts from main script?
by bliako
in thread How to import "global" variables into sub-scripts from main script?
by Polyglot
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |