mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Felix Janda <felix.janda@posteo.de>
To: musl@lists.openwall.com
Subject: Re: More GNU semantics for getopt_long?
Date: Mon, 28 Jul 2014 00:30:44 +0200	[thread overview]
Message-ID: <20140727223044.GA10396@euler> (raw)
In-Reply-To: <20140727183546.GC4038@brightrain.aerifal.cx>

Rich Felker wrote:
[..]
> > > > I noticed that there is a patch from Michael Forney on the mailing
> > > > list implementing the abbreviated options but there were not any
> > > > comments on it.
> > > 
> > > Yes that's it.
> > 
> > Thanks for revisiting the patch.
> 
> Have you tried it and confirmed that it solves your problem and
> doesn't introduce any bugs that you immediately notice? I'd like to
> include it in the upcoming release but I don't want to introduce a
> stupid regression from lack of testing...

I did some tests right now. The abbreviated options seem to work.

If the long option abbreviation is ambiguous, patched musl's
getopt_long will return the last match in the longopts array instead
of '?'.

I also noticed that 66fcde4ae4a52ae3edb1cf237ce2c22d08d7a062 seems
to have broken getopt_long: Even if optstring does not begin with
':', getopt_long will return ':' if a long option is not supplied
by its required argument.

Felix


  reply	other threads:[~2014-07-27 22:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  9:12 Felix Janda
2014-07-26  9:31 ` Rich Felker
2014-07-26 17:48   ` Felix Janda
2014-07-26 18:34     ` Rich Felker
2014-07-27 18:35     ` Rich Felker
2014-07-27 22:30       ` Felix Janda [this message]
2014-11-19 17:42         ` Rich Felker
2014-11-19 18:44           ` Felix Janda
2014-11-19 22:50             ` Rich Felker
2014-11-21 18:49               ` Felix Janda

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=20140727223044.GA10396@euler \
    --to=felix.janda@posteo.de \
    --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).