# from Michael G Schwern
# on Wednesday 28 November 2007 20:11:
>There's the additional problem that it restricts the test arguments to
> only be allowed at the end of the prove command line. This means
> switch ordering is important, which will lead to problems
> programmaticly constructing prove commands or chaining switches
> together without knowing what all the previous switches are.
Indeed. Though one could argue that such conundrums are out-of-scope
and it should just be a '--testargs' sentinel (possibly up to a --,
though the tests may need that in a literal, so it's got another
sentinel: --end-testargs, right? (Yeah, requires a trick to get Getopt
to play along.)
Making it a quoted string won't work because we're using a list context,
so we would have to deparse quotes inside that to preserve spaces.
Backslash the spaces?
# from Andy Lester
# on Wednesday 28 November 2007 12:47:
>My only concern about any of this is that it opens the door for the "I
> want to pass different arguments to different tests...."
And yes, that. Something like:
prove t --testargs-t/this.t --bar --baz
But that's going to get ugly real quick. Then you end up with something
like the old execrc or whatever where each test file (or glob
pattern -- most specific first?) has an entry.
--Eric
--
A counterintuitive sansevieria trifasciata was once literalized
guiltily.
--Product of Artificial Intelligence
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
