--- On Sun, 17/10/10, Aristotle Pagaltzis <pagalt...@gmx.de> wrote: > From: Aristotle Pagaltzis <pagalt...@gmx.de> > > Modules are poor place for evangelism about unrelated > conventions > in general, but I feel this especially strongly about > Test:: > modules with break-the-CPAN level adoption such as > Test::Deep.
That arguments you made are compelling, so I need to ask your point of view about this: #!/usr/bin/env perl use Test::Most ok 1, '1 is true'; "use Test::Most tests => 42" is loosely equivalent to: use strict; use warnings; use Test::Exception 0.88; use Test::Differences 0.500; use Test::Deep 0.106; use Test::Warn 0.11; use Test::More tests => 42; Test::Most, like Test::Class::Most, not only imports the most common testing functions, but also imports strict and warnings for you. I didn't do this lightly. I did this because I see a lot of test suites forgetting one or the other and in the case of test suites, it's terribly important to not miss those because they stop so many errors (for example, many warnings are actually symptoms of underlying bugs and that's what a test suite is about, right?). So did I do the wrong thing here? I'd love to hear pro and con arguments. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6