Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-to:marcus.boerger@post.rwth-aachen.de
Message-ID: <5.1.0.14.2.20030317203514.024cdc58@pop.t-online.de>
Date: Mon, 17 Mar 2003 20:36:52 +0100
To: Andrei Zmievski <andrei@gravitonic.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <20030317193045.GA27116@hyperion.gravitonic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] Re: zend_module_entry changes - feature request
From: marcus.boerger@t-online.de ((Marcus =?iso-8859-1?Q?B=F6rger?=))
References: <20030317193045.GA27116@hyperion.gravitonic.com>

At 20:30 17.03.2003, Andrei Zmievski wrote:
>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.


You forgot about one idea i do like much more: registering extension
classes in a seperate namespace (e.g.: the extension name).

Besides that the idea is really cool and improves introspection. What
about adding a SHORT textual info to the function/class members?

marcus