From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: getopt_long incompatibility
Date: Mon, 27 Apr 2015 13:08:56 -0400 [thread overview]
Message-ID: <20150427170856.GB17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150427165653.GB30394@mforney.org>
On Mon, Apr 27, 2015 at 09:56:53AM -0700, Michael Forney wrote:
> On Mon, Apr 27, 2015 at 12:18:16PM -0400, Rich Felker wrote:
> > I read the gnulib code but I don't see why it expects a match. From
> > the glibc code it looks to me like the ambig_list should have length 2
> > and produce an error. I don't see any reasonable way getopt_long could
> > choose between the two choices for the user without violating a
> > principle of least surprise. Do you get what's going on?
> >
> > Rich
>
> glibc only adds to ambig_list if the following condition is met:
>
> if (long_only
> || pfound->has_arg != p->has_arg
> || pfound->flag != p->flag
> || pfound->val != p->val)
>
> so I guess if all the matching option structs are the same, you're
> allowed to pick any matching option for longindex (unless you're in
> getopt_long_only).
OK, I think this behavior could be allowed. Seems useless but
harmless. I'll look at what it takes to implement it.
Rich
prev parent reply other threads:[~2015-04-27 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 6:24 Michael Forney
2015-04-27 16:18 ` Rich Felker
2015-04-27 16:56 ` Michael Forney
2015-04-27 17:08 ` Rich Felker [this message]
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=20150427170856.GB17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).