Sometimes documenting your work in POD and/or places like here can have positive side effects.
In much the same way as teaching something to someone else helps you learn it more effectively, telling someone else exactly what your program is meant to do helps you too.
And so it was with pler.
Until I wrote that the main idea of pler was to DWIM with as little typing as possible, it hadn't occured to me that it might be a good idea to allow this to be taken to almost rediculous lengths.
So I've now added the ability for pler to just try and Do What You Mean if you don't give it a full test script.
Normally you would invoke pler with something like this
pler t/02_config.t
However, if you DON'T give pler something with .t on the end, and the file name you give it doesn't exist, pler will trawl through your t directory and look for something containing what you did give it.
Obviously, sometimes that means more than one script, so pler will tell you what they were.
adam@pita:~/dist$ pler 0
More than one possible test
t/01_compile.t
t/02_config.t
t/03_messages.t
t/04_new.t
t/06_midnight.t
t/07_bulk.t
t/08_grouper.t
t/09_rawels.t
t/10_rawfcs.t
adam@pita:~/dist$
And so now we can just go with something unique to the script we want.
adam@pita:~/fids3/trunk/ITS-SIN-FIDS-ELS$ pler 2
Loading DB routines from perl5db.pl version 1.28
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
1..65
main::(t/02_config.t:27): my $config = {};
DB<1>
That means we've now made all the following equivalent
> make && perl -Mblib -d t/02_config.t
> pler t/02_config.t
> pler 2
