Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • And these cargo cults have potentially disastrous results, caused either by their mere existence or by a bad implementation.

    Take, for example, the use_warnings metric.

    While it is all well and good to encourage the use of warnings.pm, the CPANTS metric is grossly inadequate because the use of warnings is limited to 5.6 or above.

    As a result, it is impossible for a module with a 5.005 or older Perl version dependency to legally meet the criteria of the metric.

    The author is forced to a) unnecessarily increase the version dependency b) modify the module adding an unnecesary warnings::compat dependency, or c) cheat to meet the metric.

    Maybe what we really need is the equivalent of:


    no warnings 'uninitialized';


    where the programmer can set a flag to turn off items... or in this case, check them off the list.

    So, perhaps something like this:


    no kwalatiee 'pod';


    could go into Makefile.PL or some other appropriate place.

    The point is to bring the items to the programmers attention. This allows to programmer to acknowledge the issue in a manner they feel is appropriate.

    Just an idea...

    • This is the same silly pattern that we got from Perl::Critic and a number of other systems.

      They excuse the mistakes of the automated scanner by forcing every programmer everywhere to bloat their programs out with instructions to the flawed scanning systems.

      I much prefer the idea of making the automated code as smart as possible first.