Re: RFC: Remove "destructor" from PEAR class

This is actually a bug, probably the oldest one in PEAR! The PEAR class should not register itself this way. The intention behind having the "destructor" method there was to allow people to call the superclass destructor, in case it would contain something useful for all objects one day. Fixed in CVS. - Stig On Wed, 16 Jun 2004 17:08:11 +0200, Lukas Smith <smith@backendmedia.com> wrote: > > Alexey Borzov wrote: > > > as the "destructor". And when the constructor of the child class calls > > PEAR's constructor, it checks whether the class or any of the *parent* > > classes have a "destructor". Thus each class that extends PEAR, EVEN IF > > IT DOES NOT USE THE DESTRUCTOR FEATURE ITSELF, gets registered in PEAR's > > list of objects, preventing garbage collection. This creates a huge > > problem for long running scripts. > > shouldnt it be possible to just register the object if a destructor > method is defined? > > regards, > Lukas Smith > smith@backendmedia.com > _______________________________ > BackendMedia > www.backendmedia.com > berlin@backendmedia.com > > Linn Zwoch Smith GbR > Pariser Str. 44 > D-10707 Berlin > > Tel +49 30 83 22 50 00 > Fax +49 30 83 22 50 07 > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >