From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Jeff Mahoney <jeffm@suse.com>, Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Getopt improvements
Date: Fri, 28 Feb 2003 15:41:57 +0300 [thread overview]
Message-ID: <20030228154157.A10830@namesys.com> (raw)
In-Reply-To: <3E5F504A.6010902@namesys.com>
Hello!
On Fri, Feb 28, 2003 at 03:04:26PM +0300, Hans Reiser wrote:
> >>> For the simple cases (which also happen to be all we have right
> >>>now), yes, I think that my implementation is cleaner. It allows the
> >>>simple use of mutually exclusive options, through the "no" prefix, and
> >>>clearing of the other bits in a multivalue option. For now, that's
> >>>all we need - and it's a valid argument for using my code. However,
> >>>what I like about Oleg's implementation is that if you have an option
> >>>that excludes other options (even when it's not multivalue), it can
> >>>clear those bits as well.
> >>It clears them without failing, yes? Not sure I like that.
> >Hm, why should it fail?
> 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.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-28 12:41 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 [this message]
2003-02-28 12:52 ` Hans Reiser
2003-02-28 13:15 ` Oleg Drokin
2003-02-28 13:26 ` Jeff Mahoney
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=20030228154157.A10830@namesys.com \
--to=green@namesys.com \
--cc=jeffm@suse.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.