From: Jason Larson <[EMAIL PROTECTED]> > Thanks for the suggestion. I looked through the bug database before > submitting the bug and didn't find anything, but when I submitted it, > they said it was a duplicate of 11031 (guess I didn't look for the > right thing). Their comments on 11031 state: > > "This problem happens because of a bug in Perl itself, where lexical > variables are leaking out of their lexical scope. The following > program demonstrates this bug, where the lexical $foo leaks into the > safe_eval() sub defined above it. > ... > This problem is still present in PerlApp 4.0 with ActivePerl 631."
This question just come up in [EMAIL PROTECTED] as well and Jan Dubois explained this. > > I can't replicate this with my version of PerlApp. > > hmmm... Does that mean they should have said "This problem happens > because of a bug in ActivePerl itself"...? Well not really. The bug in Perl is present in my version as well. But the magic done by PerlApp when you use or require a module was slightly different in PDK 2 and 3 than it is in PDK 4 and it did not trigger the bug. Please don't ask me about details here, but I believe there was a reason for that change. Jenda =========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== There is a reason for living. There must be. I've seen it somewhere. It's just that in the mess on my table ... and in my brain. I can't find it. --- me -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
