Skip Menu |

This queue is for tickets about the AnyEvent CPAN distribution.

Report information
The Basics
Id: 53404
Status: resolved
Priority: 0/
Queue: AnyEvent

Owner: Nobody in particular
Requestors: JAWNSY [...]

Bug Information
Severity: Wishlist
Broken in: 5.23
Fixed in: (no value)

Subject: Spelling Mistakes
Download (untitled) / with headers
text/plain 796b
Hi: I discovered a spelling mistake in the POD for this package (noticable -> noticeable). We've patched it for the Debian package; you may want to apply these changes in your version control. Note we neither need nor are we asking for another release, as I think that would put undue burden on the CPAN mirrors for such a tiny issue. --- a/lib/ +++ b/lib/ @@ -23,7 +23,7 @@ many mistakes are caught at compiletime with this API. Also, some backends (Perl and EV) are so fast that the method call -overhead is very noticable (with EV it increases the time five- to +overhead is very noticeable (with EV it increases the time five- to six-fold, with Perl the method call overhead is about a factor of two). At the moment, there will be no checking (L<AnyEvent::Strict> does not
Subject: Re: [ #53404] Spelling Mistakes
Date: Tue, 5 Jan 2010 19:46:41 +0100
To: Jonathan Yu via RT <bug-AnyEvent [...]>
From: Marc Lehmann <schmorp [...]>
Download (untitled) / with headers
text/plain 2.1k
Hi! You sent a possible bug report on or via Please read this mail carefully if you want to be heard. Most likely, your report will be ignored. Please close the ticket again and sent it to the official contact address for the module in question (or send it to Why is this necessary? has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with's bugs). Still, for some people, is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of didn't make their "service" optional - you can neither opt-in nor opt-out of as a module author. Just like a spammer, forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss possibly vital bug reports (and of course it's a great impression if has lots of bug reports that are unanswered, making a module unmaintained when in fact the opposite might be true). This is why it is important that you delete/resolve your ticket. I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. Thanks a lot, Marc Lehmann <>
Delete bug misfiled to CPAN RT
Apparently, permission denied to delete my own bug report. So I'm marking it as resolved instead.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to