From: Jeff Mahoney <jeffm@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Hans Reiser <reiser@namesys.com>,
Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Getopt improvements
Date: Fri, 28 Feb 2003 08:26:12 -0500 [thread overview]
Message-ID: <3E5F6374.9040003@suse.com> (raw)
In-Reply-To: <20030228161535.C10830@namesys.com>
Oleg Drokin wrote:
> Hello!
>
> On Fri, Feb 28, 2003 at 03:52:17PM +0300, Hans Reiser wrote:
>
>
>>>>Incompatible options should fail as they represent error. Feel free to
>>>>argue with that.
>>>
>>>Hm, I am not going to argue. But we never had this kind of logic.
>>>Usually the latest-specified option was taking effect.
>>
>>Conflicts in the same command line should fail, latest command line
>>should override. Yes?
>
>
> Ok, I will think on how to implement that.
>
> Bye,
> Oleg
No, just the opposite. I'm suggesting that if smalltail and largetail
were _not_ mutually exclusive they should be first level options. Since
they _are_ mutually exclusive, then they are well suited for a second
level option.
I think that the appearance of assignment involved in specifying a
second level option makes it intuitive to believe that only the most
recently used option is the active one.
-Jeff
--
jeffm@suse.com
jeffm@csh.rit.edu
next prev parent reply other threads:[~2003-02-28 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 20:42 Getopt improvements Jeff Mahoney
2003-02-26 21:10 ` Hans Reiser
2003-02-27 6:25 ` Oleg Drokin
2003-02-27 15:39 ` Jeff Mahoney
2003-02-27 16:25 ` Oleg Drokin
2003-02-27 20:20 ` Hans Reiser
2003-02-27 21:35 ` Jeff Mahoney
2003-02-27 22:35 ` Hans Reiser
2003-02-28 0:15 ` Jeff Mahoney
2003-02-28 0:22 ` Anders Widman
2003-02-28 7:47 ` Oleg Drokin
2003-02-28 7:04 ` Oleg Drokin
[not found] ` <3E5F634D.8060901@suse.com>
2003-02-28 13:54 ` Oleg Drokin
2003-02-28 7:01 ` Oleg Drokin
2003-02-28 12:04 ` Hans Reiser
2003-02-28 12:41 ` Oleg Drokin
2003-02-28 12:52 ` Hans Reiser
2003-02-28 13:15 ` Oleg Drokin
2003-02-28 13:26 ` Jeff Mahoney [this message]
2003-02-28 15:30 ` Jeff Mahoney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E5F6374.9040003@suse.com \
--to=jeffm@suse.com \
--cc=green@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.