http://www.nntp.perl.org/group/perl.perl5.porters/2012/02/msg183037.html
The key part: >>> Ah, but it's buggy and causes mysterious failures that are hard to >>> diagnose for users after the required functionality had been removed. This >>> has been reported, and the author of IO::Async::Loop::AnyEvent has had >>> ample time to fix it. >> >>As you did to Rocco, I claim "citation needed". > >Condvars stop working, as well as programs using other event loops than >IO::Async. Sadly, he never expanded on 'stop working' in any way that allowed anybody to duplicate the problem. Also, my production code using IO::Async::Loop::AnyEvent plus AnyEvent::Impl::Perl plus condvars ... worked fine. Until the die() was added. So, yeah. Intentional gratuitous breakage. -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst commercial support, training and consultancy packages could help your team. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
