# from Andy Armstrong
# on Thursday 29 November 2007 09:08:
>On 29 Nov 2007, at 17:10, Eric Wilhelm wrote:
>>> # Run all tests
>>> $ prove --state=save -rb t/*.t
>>
>> I would rather just '--save-state', why do the "=foo,bar" thing ?
>
>Because it allows you to express what you'd like to have happen with
>the saved state.
You can express it in many ways. My question is: why choose this one?
If the option parser preserved the order of the flags, you wouldn't have
to cram that all into an '=foo,bar' opterand.
--save-state
--no-save-state
--failed-only
--failed-first
(Yes, needs more thought in the "abbreviation and short uniqueness" than
that (so --failed would mean failed-only (--failures-first?)))
I think it is more a matter of expressing "what you would like to have
happen" -- the user doesn't need to be thinking about "the saved state"
so much.
--Eric
--
"If you only know how to use a hammer, every problem begins to look like
a nail."
--Richard B. Johnson
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
