strange mod_perl variable behaviour

2004-03-05 Thread MJH
I'm completely stumped here, so I figured I'd ask to see if there's something I've missed in my reading. I have a script running under apache2(2.0.47), mod_perl (1.99_09), Registry. It uses a small class to handle certain parts of the application for me, and I'm depending on the DESTROY functi

Re: strange mod_perl variable behaviour

2004-03-05 Thread Perrin Harkins
On Fri, 2004-03-05 at 19:08, MJH wrote: > use app::utility_class; > my $var = new app::utility_class; > do stuff... If "do stuff" includes and subs that reference $var without it being passed to them, you'll create a closure. For example: sub foo { $var->bar(); } That will prevent it f

Re: strange mod_perl variable behaviour

2004-03-08 Thread MJH
On Friday 05 March 2004 07:19 pm, Perrin Harkins wrote: > > use app::utility_class; > > my $var = new app::utility_class; > > do stuff... > > If "do stuff" includes and subs that reference $var without it being > passed to them, you'll create a closure. For example: "do stuff" didn't, but t