Hi, http://pecl.php.net/package/Weakref has been created, and the standalone code should compile fine (I checked for 5_3 only but everything should be smooth for 5_4/trunk)
The next planned addition is a StrongRef class, following the exact same interface as WeakRef only that it is always valid and get() always return the ref. The reason for it is that code can switch between the two transparently. Best, On Wed, Aug 3, 2011 at 14:49, Hannes Landeholm <landeh...@gmail.com> wrote: > Good idea. I will see what I can do when I get time. > > ~Hannes > > On 3 August 2011 12:32, Pierre Joye <pierre....@gmail.com> wrote: >> hi Hannes, >> >> I would suggest to still update the RFC with the various very >> instructive comments and example use cases you use in this thread. >> Doing the same in the long run should help as well to understand the >> goals, implementations, etc., for the pecl users or for the 2nd >> attempt to get it in the core, if still desired. >> >> Cheers, >> >> On Wed, Aug 3, 2011 at 12:25 PM, Hannes Landeholm <landeh...@gmail.com> >> wrote: >>> Hello, >>> >>> We had a healthy discussion around WR and I have been able to express >>> my concerns. The consensus is clearly to put it in a PECL extension so >>> I think this discussion should move on to the practical matters of >>> doing this. I suggest aborting the vote and changing the RFC state to >>> something like "Transfered to PECL". >>> >>> ~Hannes >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >>> >> >> >> >> -- >> Pierre >> >> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org >> > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Etienne Kneuss http://www.colder.ch -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
