Jonathan Swartz wrote:
2) I have to compute the right exception paths. Doing "use lib
qw(blib/lib blib/arch)" as you suggest would only work if the tests
were
run from the main directory. e.g. If I'm in the t/ directory and do
"perl -I../lib foo.t", as I do sometimes, it ought to work as well.
Patient: Doctor doctor, it hurts when I do this!
Doctor: Then don't do that.
Yes, you can beef up your tests so that they can be run from various
directories. You can use FindBin and File::Spec->rel2abs and all
sorts of
stuff to that end. I believe blib.pm takes care of making sure @INC
works.
But really the simplest thing is to get into the habit of running
tests from
the source directory and no where else.
Ok, fair enough. :) I didn't know whether I could legitimately make
that assumption for all the automated cpan testers out there. If I
can, then I agree, it makes things easier.
I still need to hide modules by regexp. That should be easy enough to
do, even by hand.
Jon
