Re^2: Odd Apache::Reload failure

That looks like it'll do it! I didn't think of it because I'm not importing any methods from the package, but Apache::Reload uses import() to call register_module(). Well, testing explicit Reload now. If it works, I may just do away with the implicit Reloads. If not, then I'll be inserting a lot of import() calls into modules!

Comment on Re^2: Odd Apache::Reload failure

Replies are listed 'Best First'.
Re^3: Odd Apache::Reload failure by perrin (Chancellor) on Jun 05, 2008 at 20:45 UTC
This, by the way, is another example of why I think using import() for things other than importing is a bad idea. If the docs had said you must call Apache::Reload::register_module() instead of doing it for you magically when you use Apache::Reload, you wouldn't have wondered why it wasn't working.	[reply]
Re^4: Odd Apache::Reload failure (not importish) by tye (Sage) on Jun 05, 2008 at 22:33 UTC
Good point. Have you deleted strict.pm yet? Perhaps Module::Load::Conditional should use a test like autouse does to verify whether or not import() is "special". (autouse throws up if you try to use it on a module whose import() didn't come from Exporter). Note that I need to file a bug against autouse because it doesn't notice that it can still break things even when Exporter::import() is used because it doesn't deal with export_fail(). - tye	[reply]