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
> z
At 20:38 17.03.2003, Andrei Zmievski wrote:
On Mon, 17 Mar 2003, Marcus Börger wrote:
> You forgot about one idea i do like much more: registering extension
> classes in a seperate namespace (e.g.: the extension name).
That may be nice, but requires an active effort on the extension
authors' part.
On Mon, 17 Mar 2003, Marcus Börger wrote:
> You forgot about one idea i do like much more: registering extension
> classes in a seperate namespace (e.g.: the extension name).
That may be nice, but requires an active effort on the extension
authors' part.
> Besides that the idea is really cool and
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. Th
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)
