in reply to Ignoring warnings

How do you convince someone that warnings are there for a reason?

You don't have to convince him; you just have to get him to change his behavior. Isn't there a quality rating system for CPAN modules? I don't know how thorough or how effective it is, but if "build warnings" are considered unacceptable, that may get his attention.

My personal feeling, which may be similar to yours, is that compile-time warnings are unacceptable. My experience is that they are usually the result of code that is either potentially dangerous or is not standard-compliant.

emc

At that time [1909] the chief engineer was almost always the chief test pilot as well. That had the fortunate result of eliminating poor engineering early in aviation.

—Igor Sikorsky, reported in AOPA Pilot magazine February 2003.

Replies are listed 'Best First'.
Re^2: Ignoring warnings
by jdhedden (Deacon) on Dec 11, 2006 at 19:58 UTC
    You don't have to convince him; you just have to get him to change his behavior. Isn't there a quality rating system for CPAN modules? I don't know how thorough or how effective it is, but if "build warnings" are considered unacceptable, that may get his attention.
    Well, it is possible to write a review against a module and rate it. However, I have seen that venue become a vehicle for retaliatory activities.

    Then there is CPANTS. However, they don't build modules, leaving that activity to CPAN testers.

    As to CPAN testers, there is no criteria related to build warnings - just 'make test' results.

    So AFAIK, there is no feedback mechanism for build warnings other than reporting them to the developer (as I did, along with a patch) with RT being the most effective method for that purpose.

    Remember: There's always one more bug.
[reply]

In Section Meditations