Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44584CA9.2040609@bfoz.net>
Date: Tue, 02 May 2006 23:24:41 -0700
User-Agent: Thunderbird 1.5.0.2 (X11/20060430)
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: zend_class_entry.create_object
From: bfoz@bfoz.net (Brandon Fosdick)

When registering a new class, what are the consequences of setting zend_class_entry.create_object = NULL? INIT_CLASS_ENTRY() defaults it to NULL, but the tutorial I'm looking at sets it to the address of a function immediately afterwards. 

My concern is that setting this allows the engine to call a constructor-like-function behind my back. I'd rather handle such things while handling calls to new(). Is that possible? Is it even a good idea?

The tutorial code provides a function for zend_class_entry.create_object that returns a populated zend_object_value. Presumably that's a useful thing to do, and if I don't have a function there I would need to find some other means of supplying the zend_object_value to the engine. Can I do that in a new() handler? How?