Front page | perl.perl5.porters |
Postings from January 2012
Paul, I know, Marc is very hard man to talk, but why don’t you and Marc come to mutual understanding? Your ::Loop::AnyEvent goes into AE's internals. It's not a good point of interaction with other modules You abuse Marc's module, so he insert a protection from abusing. If I know, that something on CPAN will not work, or will work badly with my module I prefer to protect from such interaction. Just try to talk with him and many users of AE and IO::Async will win instead of stupid war between AE and IO::Async On Thu, Jan 19, 2012 at 4:42 AM, Paul LeoNerd Evans <leonerd@leonerd.org.uk>wrote: > On Thu, Jan 19, 2012 at 01:01:39PM +0100, demerphq wrote: > > > Interoperability requires cooperation from the author, and he's been > known to break it for modules he doesn't like. Ask Paul Evans and/or Matt > Trout about this: > > > > > > > https://metacpan.org/source/MLEHMANN/AnyEvent-6.13/lib/AnyEvent.pm#L1396 > > > > > IMO AnyEvent should be removed from CPAN until this code is removed, > > it seems inappropriate for CPAN to host code that forbids you from > > using something else on CPAN. > > That seems a -little- OTT as a response, surely? Perhaps a far better > solution would simply be to bring this change to more people's > attention, and point out that other alternatives exist (namely > IO::Async, POE and Reflex come to mind); and that people should be free > to decide which one(s) they want to use. > > -- Best wishes, Vladimir V. Perepelitsa aka Mons Anderson <inthrax@gmail.com>, <mons@cpan.org> http://github.com/Mons