lkml.org 
[lkml]   [2004]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: new tool: blktool
[...]

> Yep, it's more like ethtool(8) or cvs(1) in its syntax. There is big
> difference in usability (for me anyway) between "command [options]..."
> and an unordered list of --args. Especially as the list of commands
> grows longer. It provides more structure.
>
> Each command can have options, --foo-bar=baz if you like, I suppose.


I would rather see --option=xyz than option xyz. End users are going to
be using it in scripts and in the event a parameter becomes "", then it
will become --option1= --option2=def instead of option1 option2 def. I
would find it easier to parse, --option= is easy to ignore, option
option has to be recognized as an empty option instead of using option
as the first option's argument.

Just my opinion,
-david

begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.057 / U:4.636 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site