Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Andrei Zmievski <andrei@gravitonic.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <20030317193045.GA27116@hyperion.gravitonic.com>
References: <20030317193045.GA27116@hyperion.gravitonic.com>
Content-Type: text/plain
Organization: 
Message-ID: <1047928660.17032.141.camel@hasele>
Mime-Version: 1.0
Date: 17 Mar 2003 14:17:40 -0500
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: zend_module_entry changes - feature request
From: sterling@bumblebury.com (Sterling Hughes)

On Mon, 2003-03-17 at 14:30, 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.

What about adding an introspection element to the zend_module_entry,
that would allow it to serve up such information per-request.  This way
private functions could be hidden, necessary classes and datastructures
could be exposed, and it would be extensible to boot?

-Sterling


> 
> -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)
-- 
"Science is like sex: sometimes something useful comes out, 
but that is not the reason we are doing it." 
    - Richard Feynman