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.

use Perl

All the Perl that's Practical to Extract and Report

Config::JSON dependencies More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

It's packaged badly (Score:1)

by Alias (5735)

Tests that do not impact on functionality should always be optional, for two reasons.

Firstly, there's the issue of code bloat.

Test::Perl::Critic in particular has fairly serious dependencies (since it needs to install PPI).

But secondly, it results in false-positive failures.

That is, by making a test script for say POD checking, you are essentially saying that the POD for a module is SO important, if for some unknown reason there's a single small bug in the POD, you as the author would rather have them not u
- Re:It's packaged badly (Score:1)
  
  by DAxelrod (4649) on 2007.07.11 19:53 (#56185) Journal
  
  Tests that do not impact on functionality should always be optional, for two reasons.
  
  OK, make that THREE reasons.
  Nobody expects the CPANish imposition! :)
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.