I suspect that we can get past the CLIP issues in ARC with a reasoned
approach; the proposal to have meta options prior to the subcommand
has compelling usability advantages that improve the user experience.
As far as the ambiguity issue, we have the same problem today with
regular options eg:
asadmin --boolOption operand
Lloyd
On Aug 20, 2008, at 5:14 PM, Bill Shannon wrote:
> Jane Young wrote:
>> Hi Kedar et al,
>> >In v3, can I say "asadmin --target foo list"? That is, can all the
>> >common arguments that really apply to asadmin itself rather than the
>> >subcommands be specified *before* the subcommand?
>> This is *not* CLIP compliant. Please see: http://www.opensolaris.org/os/community/arc/caselog/1999/645/spec-html/
>
> Stupid CLIP. :-(
>
>> Also, there is ambiguity if options are specified *before* the
>> subcommand.
>> Consider the example:
>> "asadmin --option-name foo bar" What if --option-name is a boolean
>> option. So is foo treated as an option value to option-name or is
>> it treated as a subcommand? Note that boolean option does not
>> require a option value.
>
> Having options with optional values is ambiguous. It doesn't matter
> if
> the options come before or after the subcommand. Does CLIP really
> allow that?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>