Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11474
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 22 Jul 2004 20:44:38 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <87496551.20040722204438@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>
Cc: Andrei Zmievski <andrei@gravitonic.com>,
	Zeev Suraski <zeev@zend.com>, stas@zend.com,
	PHP Internals <internals@lists.php.net>
In-Reply-To: <5.1.0.14.2.20040721231339.0272f008@127.0.0.1>
References: <20040722060130.GA10387@hyperion.gravitonic.com>
 <5.1.0.14.2.20040721231339.0272f008@127.0.0.1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Internal properties
From: helly@php.net (Marcus Boerger)

Hello Andi,

Thursday, July 22, 2004, 8:16:10 AM, you wrote:

> At 11:01 PM 7/21/2004 -0700, Andrei Zmievski wrote:
>>Hi,
>>
>>I saw this in zend_opcode.c zend_cleanup_class_data():
>>
>>        /* Note that only run-time accessed data need to be cleaned up,
>>                 * pre-defined data can not contain objects and thus are 
>> not probelmatic */
>>
>>Which lead me to look into zend_declare_property() and I noticed that
>>you cannot declare properties that are objects/arrays/resources. Is
>>there a good reason for disallowing extension authors to do that?

> The problem is that objects and resources can't really stay alive in 
> between requests because those mechanisms are shutdown at rshutdown. Arrays
> also can't stay alive because they need to be emalloc()'ed or they won't 
> work with the engine.

I rememer seeing a patch that gave anything that was allocated (either
malloc or emalloc or whatever_alloc) a destructor function pointer alias
free. Wouldn't that solve any related problem?

-- 
Best regards,
 Marcus                            mailto:helly@php.net