in reply to Mod_perl, Memory Leaks and WeakRef

You don't call DESTROY, you just undef your object, and break all the circular references in DESTROY.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Mod_perl, Memory Leaks and WeakRef
by djantzen (Priest) on Dec 26, 2003 at 00:23 UTC

    Of course I still have to find all of the references to the object otherwise I'll just decrement the refcount of the object and it won't be destroyed. Point taken though about the role of DESTROY versus undef.

    "The dead do not recognize context" -- Kai, Lexx
[reply]

In Section Seekers of Perl Wisdom