Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11457
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20040721231339.0272f008@127.0.0.1>
Date: Wed, 21 Jul 2004 23:16:10 -0700
To: Andrei Zmievski <andrei@gravitonic.com>,Zeev Suraski <zeev@zend.com>,
 stas@zend.com
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <20040722060130.GA10387@hyperion.gravitonic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: Internal properties
From: andi@zend.com (Andi Gutmans)
References: <20040722060130.GA10387@hyperion.gravitonic.com>

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 think it'd be quite complex to change this behavior 
and the work around probably needs to be in the extension depending on how 
bad it is to recreate these or somehow cache them for rinit.

>Alternatively, do you suggest using zend_hash_update() on class
>properties even though I really need this property to be static so its
>shared by all instances of the class?

If these are per-request statics it can probably be solved.

Andi