Hi,
You can look into proposal patch that implements support for constants and
static methods for internal classes. The original patch was written by
Michael and improved by me.
The patch is maden for "easiest" usage and it doesn't support internal
array/constants properties (they weren't supported before).
Unless something thinks array/constants are badly needed (we think they
probably aren't) we prefer to keep it simple like this.
Support for array and constant properties will require additional
complicated API.
Thanks. Dmitry.
Hi Dmitry Stogov, you wrote:
You can look into proposal patch that implements support for constants and
static methods for internal classes. The original patch was written by
Michael and improved by me.
Is it my (mailers) fault or didn't the patch make it through?
Thanks,
Michael - < mike(@)php.net
Hi Dmitry Stogov, you wrote:
The patch is maden for "easiest" usage and it doesn't support internal
array/constants properties (they weren't supported before).
So why burden the weigh of allocation, initialization, destruction
and freeing on the extension developer? This will force every extension
writer to implement a kind of my dup_zval() function, wouldn't it?
And as there's not much reference devs will spam the list on how
to use static properties right. I think we could avoid this by
stretching the minimalistic approach a bit and provide at least
a zend_init_static_properties().
Thanks a lot,
Michael - < mike(@)php.net
I wrote:
So why burden the weigh of allocation, initialization, destruction
and freeing on the extension developer? This will force every extension
writer to implement a kind of my dup_zval() function, wouldn't it?
And as there's not much reference devs will spam the list on how
to use static properties right. I think we could avoid this by
stretching the minimalistic approach a bit and provide at least
a zend_init_static_properties().
One note more though :-/
If we leave out the zend_update_static_property() API,
extension developers need to reinvent the wheel again
and again.
Regards,
Michael - < mike(@)php.net