From: Felix Janda <felix.janda@posteo.de>
To: musl@lists.openwall.com
Subject: Re: More GNU semantics for getopt_long?
Date: Wed, 19 Nov 2014 19:44:50 +0100 [thread overview]
Message-ID: <20141119184449.GA1608@euler> (raw)
In-Reply-To: <20141119174227.GL22465@brightrain.aerifal.cx>
Rich Felker wrote:
> I'd like to resume working on getting this integrated, especially
> since one of the main Roadmap goals for 1.1.6 is solving the remaining
> issues Alpine Linux is matching musl for, of which getopt_long is one.
Thanks for coming back to this.
> > 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.
>
> Is this still broken, and if so, could you provide a short testcase I
> could use for checking it and figuring out what's wrong?
Nothing has changed. Below is a testcase.
--Felix
#include <stdio.h>
#include <getopt.h>
int main(void) {
struct option opts[2] = {{"opt", 1, NULL, 'o'}, {0, 0, 0, 0}};
int ret;
ret = getopt_long(2, (char *[3]){"a", "--opt", 0}, "", opts, NULL);
if (ret != '?') printf("'%d' != '%d'\n", ret, '?');
return 0;
}
next prev parent reply other threads:[~2014-11-19 18:44 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
2014-11-19 17:42 ` Rich Felker
2014-11-19 18:44 ` Felix Janda [this message]
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=20141119184449.GA1608@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).