It looks like extensions that don't use this new API will continue to
work, they'll just leak when __set() is used with them.
We should bump the zend API number to allow extensions to make use of
the new API.
--Wez.
On Wed, 29 Mar 2006 14:28:43 -0000
tony2001@php.net ("Antony Dovgal") wrote:fix bug #36898 (__set() leaks in classes extending internal ones)
Added:
ZEND_API void zend_object_std_init(zend_object *object,
zend_class_entry *ce TSRMLS_DC) ZEND_API void
zend_object_std_dtor(zend_object *object TSRMLS_DC)
to initialize and destroy zend_object structsWithout minimizing the importance of this fix, I wonder two things. The
first is about adding such things right when we are in the RC phase for
5.1.3, it sounds a bit risky to me.The second problem is about extension available in pecl as well, all of
a sudden, it is not possible to compile them with the last php 5.1
version, and there is no possible way now to compile them.What's about a Zend api version change? and then allows an extension to
be compiled with previous PHP versions.Regards,
--Pierre
It looks like extensions that don't use this new API will continue to
work, they'll just leak when __set() is used with them.
Yes, as soon as you do not use these two new functions, they will
"only" leak, like before ;-)
I was talking about the ones affected by this commit.
We should bump the zend API number to allow extensions to make use of
the new API.
It should be the case more often, it is getting really hard to know
when and what was introduced (even harder as there is no changelog for
internals changes).
--Pierre