On 10.08.2016 at 13:38, Kalle Sommer Nielsen wrote: > 2016-08-10 12:59 GMT+02:00 Nikita Popov <nikita....@gmail.com>: >> On Wed, Aug 10, 2016 at 12:52 PM, Christoph M. Becker <cmbecke...@gmx.de> >> wrote: >> The simplest way to fix ext/xml in particular is probably to migrate it to >> use an object instead of a resource. > > If my memory strikes me right, then we did do this for ext/gmp too a > while back for the operator overloading (I even think it was you that > did that?). Maybe it would be time to evaluate the situation in 7.2, > for extensions that still use resources[1] that could be affected by > similar issues and adapt them hereafter.
I would welcome that, but it appears to be a lot of work. BTW: ext/mcrypt is deprecated as of PHP 7.1 so I don't think a rework is apt. Furthermore, we may consider to deprecate some other extensions (stas has a draft RFC for that). IIRC, ext/odbc/birdstep doesn't even work/is not used. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
