On Sun, Jul 03, 2005 at 10:04:52AM +0200, demerphq wrote:
> Well, its more what i was trying to do. Just ask yourself "how do a i
> write module that is exactly like Test::More except one of the tests
> has overloaded behaviour?
You don't. I love that answer.
You write your module with its one exported function and call it something
different than what Test::More calls it, because unless you're doing
something really clever and transparent it is different. Then you release
your module to CPAN and let the user decide if they want to use Test::More
with your module.
use Test::More tests => 4;
use Your::Module;
or maybe its just
use Your::Module tests => 4; # don't need no stinking Test::More.
You don't try to shove Test::More onto people. Your module does its thing.
Small, sharp tools.
There are sneaky ways to override Test::More's functions, or any other
module's, but they're not worth elaborating on as 99.99% of the time its
the wrong thing to do.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked and wrong to have broken inside and peeked at the
implementation and then relied upon it.
-- tchrist in <[EMAIL PROTECTED]>
