forget about mod_perl for a moment. yes, true, Perl's built-in require will not reload a module if it's already in %INC. but that's doesn't mean a Perl environment cannot un-cache that entry so it will be reloaded. consider the code below, pretend that loop is a long-lifetime server, Tk type application, vi or emacs with Perl embedded: use Module::Reload (); do { Module::Reload->check; require Foo; } while (<STDIN>); Module::Reload checks the mtime of Foo.pm (and all loaded modules) on disk, if it has changed since the last time it was require'd, it will be reloaded. this is perfectly valid Perl, the language supports this feature. i'm quite certain your code be changed to adapt to such an environment.
- Re: global variables and reparsin... Marc Lehmann
- Re: global variables and reparsin... Doug MacEachern
- Re: global variables and repa... Marc Lehmann
- Re: global variables and repa... Doug MacEachern
- Re: global variables and reparsing question (low priori... Gustavo Duarte
- Re: global variables and reparsing question (low p... Marc Lehmann
- Re: global variables and reparsing question (l... Doug MacEachern
- Re: global variables and reparsing questio... Marc Lehmann
- Re: global variables and reparsing que... Doug MacEachern
- Re: global variables and reparsin... Marc Lehmann
- Re: global variables and repa... Doug MacEachern
- Re: global variables and repa... Marc Lehmann
- Re: global variables and repa... Perrin Harkins
- RE: global variables and reparsing question (low priori... Geoffrey Young
- Re: global variables and reparsing question (low p... Marc Lehmann
- [OT] "Tone" on this list Eric Strovink
- Re: global variables and reparsing question (l... ___cliff rayman___
- Re: global variables and reparsing question (l... Doug MacEachern