Re: Re: zend_module_entry changes - feature request
| From: | Tal Peer | Date: | Tue, 18 Mar 2003 14:30:21 +0000 |
| Subject: | Re: Re: zend_module_entry changes - feature request | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-84@lists.php.net to get a copy of this message | ||
On Mon, 17 Mar 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.
>
This way looks ok to me too. I think it can be done by adding an HashTable
of zend_class_entry's to the zend_module_entry and then passing its
address to zend_register_internal_class (which will update it).
The only problem with that is that it will require modifying any extension
that registers classes.
Tal
> -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)
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
Tal Peer
tal@php.net