On Tue, 2004-03-30 at 19:28, Stas Bekman wrote: > Garth Webb wrote: > > I have a question about Apache::StatINC and reloading exported methods. > > Garth, Apache::StatINC is deprecated and no longer maintained. Please use > Apache::Reload instead (mp1 version on CPAN, mp2 version is a part of the core). > > > Apparently methods that are exported from a module do not get reloaded > > when the module changes on disk (see the test script and test module > > below). > > That's right. Please read: > http://perl.apache.org/docs/2.0/api/Apache/Reload.html#Problems_With_Reloading_Modules_Which_Do_Not_Declare_Their_Package_Name
So I've played around with Apache::Reload, and I'm a little confused. I get the same behavior with Apache::Reload that I got under Apache::StatINC (i.e. use of exported method names leads to those methods not being reloaded), however Apache::Reload doesn't provide any way to undef functions which seemed to 'fix' the problem under Apache::StatINC. The above link to "Problems With Reloading..." doesn't seem to apply here since my module does use the correct 'package Module;' line at the top. Furthermore, checking with Apache::Status, I don't see my test function imported into the Apache::Reload namespace as it warns with modules that don't declare their package. Is there a work around for this? Have I missed something? If it were up to me, all these function calls would be fully qualified, but this is a shared code base that has been at my company longer than I have. Thanks! -- |- Garth Webb -| |- [EMAIL PROTECTED] -|
signature.asc
Description: This is a digitally signed message part
