Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 17 Mar 2003 14:30:46 -0500
To: PHP Internals <internals@lists.php.net>
Message-ID: <20030317193045.GA27116@hyperion.gravitonic.com>
Mail-Followup-To: Andrei Zmievski <andrei@gravitonic.com>,
	PHP Internals <internals@lists.php.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: Re: zend_module_entry changes - feature request
From: andrei@gravitonic.com (Andrei Zmievski)

Tal,

I guess you just want to find out which classes an extension defines.
I don't think the current architecture allows for it.

There are two ways of going about it:

1. Keep track of extension classes with a HashTable (or list) in
zend_module_entry. This list would be updated when
zend_register_internal_class() is called.

2. Add a field called module_number to zend_class_entry.

I think the first one would be more appropriate, but I welcome other
comments.

-Andrei                                       http://www.gravitonic.com/

For society, it's probably a good thing that engineers value function over
appearance.  For example, you wouldn't want engineers to build nuclear power
plants that only _look_ like they would keep all the radiation inside.
                                (Scott Adams - The Dilbert principle)