* Andy Armstrong <[EMAIL PROTECTED]> [2007-11-29 16:10]:
> $ prove --state=fail,all,save
>
> ?
>
> (option order matters, 'fail' adds the failed tests to the run
> queue, 'all' adds everything, list is de-duped so the failures
> run first, saved for next time)
Why this mental overhead? Do they really have to be ordered? Is
there any way that any other order would do anything remotely
useful? Would `save,fail,all` be useful? Or `all,save,fail`?
Every order I can think of besides the one you gave is pretty
useless in an order-sensitive scheme.
So I think the order of actions should be predetermined, in which
case I’m with Eric – I think these should be regular options.
Plus, I don’t think it’s very descriptive to use `state` in the
names of the options at all. So that would be something like:
--save-fails
--only-fails
--fails-first
For grouping purposes, just give them single-letter aliases, eg.
`-S`, `-O`, and `-F`.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
