On 26 Oct 2007, at 18:05, Eric Wilhelm wrote:
# from Jonathan Swartz
# on Friday 26 October 2007 06:53:
I'd like to avoid actually running a single script per class, for
efficiency reasons - i.e. I agree with Ovid and Adrian here:
http://use.perl.org/~Ovid/journal/31172
It seems like it
On 12 Nov 2007, at 17:00, Adrian Howard wrote:
E.g. if something like http://testanything.org/wiki/index.php/Test_Groups
ever gets sorted that would be a natural place to split separate
tests. I also want to do something like:
I'm in the http://testanything.org/wiki/index.php/Test_Blocks ca
# from Adrian Howard
# on Monday 12 November 2007 09:00:
>On 26 Oct 2007, at 18:05, Eric Wilhelm wrote:
>> Building it as a TAP::Harness plugin sort-of implies that the tap
>> stream contains diagnostics which tie the results to a given class.
Note: that was my "case against".
But I also wrote:
Hi!
I'm currently thinking about a new CPANTS metric (and I even have a
half-finished implementation..), and I'd like to get some feedback on
it, before spending more time on it (or even releasing it..)
The metric will be called prereq_matches_use and shall check if all the
modules used in a d
# from Thomas Klausner
# on Monday 12 November 2007 12:05:
> check if all the modules used in a dist are also listed as a prereq
> ... by parsing Build.PL or Makefile.PL
How do you propose to address system-dependent requirements? (e.g. "$^O
eq 'MSWin32'" issues.) If you do not execute the Mak
Hi Thomas,
* Thomas Klausner <[EMAIL PROTECTED]> [2007-11-12 21:10]:
> The metric will be called prereq_matches_use and shall check if
> all the modules used in a dist are also listed as a prereq.
> (prereq is either gatherd directly from Meta.YMLs 'requires',
> by parsing Build.PL or Makefile.PL)
Thomas Klausner wrote:
I'm currently thinking about a new CPANTS metric (and I even have a
half-finished implementation..), and I'd like to get some feedback on
it, before spending more time on it (or even releasing it..)
The metric will be called prereq_matches_use and shall check if all
the
> The metric will be called prereq_matches_use and shall check if all the
> modules used in a dist are also listed as a prereq.
I find this odd.
if I check a prereq for mod_perl (.pm) I know I have the 50 some modules
that come with a mod_perl distribution. check for LWP and I know I have
HTTP
