Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12257
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20040819103812.08419700@localhost>
Date: Thu, 19 Aug 2004 10:53:46 +0300
To: "Sara Golemon" <pollita@php.net>
Cc: internals@lists.php.net
In-Reply-To: <20040819053221.32797.qmail@pb1.pair.com>
References: <4123D1B5.3080203@caedmon.net>
 <20040819090436.788cd2bf.tony2001@phpclub.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] Class Destruction / Reloading
From: zeev@zend.com (Zeev Suraski)

At 08:32 19/08/2004, Sara Golemon wrote:
> > Well, some time ago I wrote a small functions, that does exactly the same:
> >
> > PHP_FUNCTION(unregister_class)
> > {
>*snip*
>
>Barring some stylectic differences and a check to make sure it's not an
>internal class, that's precisely what I gave sean in
>shiva_destroy_class()....
>
>But just to be clear, I don't think it's a good idea, and I'll wager dollars
>to doughnuts that it destablizes the active request if not the entire
>engine.

 From the technical perspective, it's actually easy to implement in a 
rock-solid manner.  Don't kill the class completely but just clean any 
functions/properties inside of it, and mark it as dead.  Then patch the 
class declaration begin code to check for this flag, and reuse the class 
structure instead of complaining about reregistering a class.  There might 
be some more cleanup necessary in PHP 5, but if any, it shouldn't be too 
complicated.

But I agree with you that it's a bad idea :)

Zeev