Ethan Quach wrote: > > > Frank Ludolph wrote: >> OK, but I'm still concerned that the commands be easy to remember. A >> user shouldn't have to remember whether <svcname> requires -n in one >> command, but not in another. >> >> One alternative is that there are no operands, only options. But >> "installadm start -n <svcname>" seems a little overkill. Still, it >> would be acceptable. >> >> Another alternative would be: if a subcommand has only one required >> option and no optional options, e.g. start <svcname>, that option >> should be an operand. Subcommands having multiple options, whether >> required or not, have only options and no operands. A slightly more >> complex rule to learn, but not too likely to err. >> >> I feel either is acceptable. > > I like the second alternative. But optional option flags should be > okay right? e.g. > > installadm list > installadm list serviceFoo > installadm list -m > installadm list -m serviceFoo > "Installadm list -m" should not be allowed. CLIP guideline #7 says that option arguments should not be optional. Could you send me the proposed syntax for installadm list so that I can review it more carefully?
Frank
