Re: Re: Internal properties

From: Date: Thu, 22 Jul 2004 23:26:40 +0000
Subject: Re: Re: Internal properties
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-11491@lists.php.net to get a copy of this message
Yeah but besides hurting performance that would waste an additional pointer of storage for each memory block. Not something I'd like to do. Andi At 12:05 AM 7/23/2004 +0200, Marcus Boerger wrote:
Hello Andi, i remember something where each zval had pointer to a free function to free it's memory. regards marcus Thursday, July 22, 2004, 9:00:27 PM, you wrote: Don't quite understand what you're suggesting.. Sorry. Can you please explain it again? At 08:44 PM 7/22/2004 +0200, Marcus Boerger wrote:
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
-- Best regards,
 Marcus                            mailto:helly@php.net


« previous php.internals (#11491) next »