Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12248
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 32822 invoked by uid 1010); 19 Aug 2004 05:32:21 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 32798 invoked by uid 1007); 19 Aug 2004 05:32:21 -0000
Message-ID: <20040819053221.32797.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <4123D1B5.3080203@caedmon.net> <20040819090436.788cd2bf.tony2001@phpclub.net>
Date: Wed, 18 Aug 2004 22:32:20 -0700
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Posted-By: 64.142.6.231
Subject: Re: [PHP-DEV] Class Destruction / Reloading
From: pollita@php.net ("Sara Golemon")

> 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.

Not to be too blunt, but I gave him that extension so he'd have some rope to
hang himself with (or maybe learn something useful...)

-Sara