[tapx-dev] TAP::Parser - Dump execrc?
Eric Wilhelm
scratchcomputing at gmail.com
Mon Mar 12 16:14:00 GMT 2007
# from Ovid
# on Monday 12 March 2007 05:00 am:
>What about 't/driver' (no extension) and if someone wants a different
>location:
Why not just './exec' (or './driver', './tap.driver', './test.driver',
or './tap.exec')? (I don't like the potential directory name clash in
t/.)
> runtests --driver path/to/driver
>
>The --execrc and --exec switches would go away entirely.
Isn't --driver ::= --exec? I'm in favor of dropping execrc, but I'm not
sure what's wrong with --exec.
>The driver script would be assumed to be executable. On Windows it
>might have to be:
>
> runtests --driver 'perl path\to\driver'
Aside: The current --exec handler in runtests is naive. Needs to
handle "path to\perl" and such. Too bad the OS which is most likely to
have that problem doesn't support symlinks, eh? I guess there's always
the .bat file.
>someone should be allowed
>to write the driver program in any language they want.
Or symlink it to a binary.
--Eric
--
The more you learn about Linux, the more you hate Windows.
--Gary Varnell
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
More information about the tapx-dev
mailing list