public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mlichvar at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug argparse/28081] getopt_long doesn't return error on ambiguous option Date: Mon, 19 Jul 2021 07:48:08 +0000 [thread overview] Message-ID: <bug-28081-131-BLNRD1sPFm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28081-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28081 --- Comment #5 from Miroslav Lichvar <mlichvar at redhat dot com> --- FWIW, the getopt code checks also for a different flag, not just val and has_arg. A minimal workaround, at least when the struct config is not reallocated, is to point the flag to the val itself, e.g. opts[i].flag = &opts[i].val; -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-07-19 7:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-12 15:55 [Bug argparse/28081] New: getopt_long doesn't return error on ambigouos option mlichvar at redhat dot com 2021-07-12 16:01 ` [Bug argparse/28081] getopt_long doesn't return error on ambiguous option mlichvar at redhat dot com 2021-07-12 16:12 ` schwab@linux-m68k.org 2021-07-12 16:15 ` mlichvar at redhat dot com 2021-07-12 17:56 ` schwab@linux-m68k.org 2021-07-13 7:34 ` mlichvar at redhat dot com 2021-07-19 7:48 ` mlichvar at redhat dot com [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=bug-28081-131-BLNRD1sPFm@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).