Skip Menu |

This queue is for tickets about the indirect CPAN distribution.

Report information
The Basics
Id: 48958
Status: rejected
Priority: 0/
Queue: indirect

People
Owner: Nobody in particular
Requestors:
Cc:
AdminCc:

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



Subject: please consider renaming to warnings::indirect
There is already warnings::method, warnings::unused and warnings::DynamicScope so please consider renaming to warnings::indirect, it is kind of a tradition :) Thank you
Hello "nobody". It won't happen, and this for several reasons : - People already know the "no indirect" motto and they put it in their code, sometimes even in production. Changing now would break their code for what is only a cosmetic change. I really despise this lack of manners that just seems too frequent in many open-source projects, so there's no way I'd do this. - The warnings:: prefix would suggest that it is using the quirky warnings::register feature, and this even if it's not. - indirect doesn't just throw warnings. - Finally, it was actually written before all of these modules. At that time, I considered naming it "warnings::indirect", but I rejected the idea for reasons 2 and 3. If your sense of traditions is stronger than your pragmatism, nothing stops you from writing a warnings::indirect. Vincent.