Sorry, but that is simply fatuous pseud-OO.
You pull in nearly 300 modules to do nothing more than: system '/usr/sbin/httpd';
Well yes, but my point is that a single object instantiation and method call can be something trivial - e.g. adding two numbers...
perl -MMath::BigInt -E'say Math::BigInt->new(400)->badd(2)'
(400's big enough to justify Math::BigInt, right?) ... or something complex - e.g. serving HTTP. (If you don't like the Apache example, then pure Perl Web servers such as Starman are usually not much more than an instantiation plus method call.)
Quite frankly, I cannot see any merit in your module over using App::Prove myself.
App::Reprove does a different task. App::Prove runs one or more test cases that are on the local disk. App::Reprove takes the name of an already installed module, finds its test cases on CPAN, downloads them into a temp dir and runs App::Prove on them.
But then, I can see no merit in App::Prove over using the prove command directly either.
[tai@miranda (pts/2) ~]$ cat `which prove` | head -n 13 #!/usr/bin/perl eval 'exec /usr/bin/perl -S $0 ${1+"$@"}' if $running_under_some_shell; #!/usr/bin/perl -w use strict; use App::Prove; my $app = App::Prove->new; $app->process_args(@ARGV); exit( $app->run ? 0 : 1 ); __END__
In reply to Re^7: Should I upload it on CPAN?
by tobyink
in thread Should I upload it on CPAN?
by llancet
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |