Re: package scoped my() variable in module under mod

OK, I've narrowed this down to something funky in Exporter. Removing all traces of Exporter from the UserCache module and calling subs by fully qualified name in the Apache Auth* handlers has completely fixed it and life has returned to normal - ie my() works as expected.

I'm going to have much more of a poke through the mod_perl mailing lists now and see if this is a manifestation of the accidental closure issue.

Thanks for helping me bounce this around. If anyone has any ideas why this behaviour happens when using Exporter as above then please please let me know :)

Cheers!

Comment on Re: package scoped my() variable in module under mod_perl 5.6 vs 5.8

Replies are listed 'Best First'.
Re^2: package scoped my() variable in module under mod_perl 5.6 vs 5.8 by perrin (Chancellor) on Sep 21, 2005 at 15:57 UTC
It would not be an accidental closure, since what you have here is an intentional closure. If using Exporter breaks the closure, the right thing to do is to check the Perl changelog for bits about that and if you don't see anything, make a small example and post it first on the mod_perl list and then on perl5-porters.	[reply]