On 02.02.2019 at 09:35, Joe Watkins wrote: > Some time ago I brought this up for discussion, and last night was reminded > of it's existence, and so this morning rebased and reworked the patch a > little based on the feedback I got back then. > > Since it was long ago, and there's no particular rush, I don't intend to > open voting until the current policy adjustment RFC's are resolved, but > wanted to give everyone a heads up and ask for any feedback you may have at > this time. > > https://wiki.php.net/rfc/weakrefs
Overall I like this. Thanks! However, calling this class WeakRef would introduce a potential BC break, and would be a particular issue regarding the PHP manual, which does not allow to document two classes with exactly the same name. Even if Etienne would officially cease the further development of PECL/Weakref[1], having a class with the same name appears to be confusing at best. Maybe another name should be chosen for the class? Or maybe we should finally introduce the \PHP namespace? [1] <https://pecl.php.net/package/Weakref> -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
