public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/26725] New: regcomp.c uses unusual syntax for function pointers Date: Sat, 10 Oct 2020 10:42:31 +0000 [thread overview] Message-ID: <bug-26725-132@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26725 Bug ID: 26725 Summary: regcomp.c uses unusual syntax for function pointers Product: glibc Version: 2.32 Status: UNCONFIRMED Severity: minor Priority: P2 Component: regex Assignee: unassigned at sourceware dot org Reporter: bruno at clisp dot org CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 12895 --> https://sourceware.org/bugzilla/attachment.cgi?id=12895&action=edit Proposed patch regcomp.c uses a syntax for function pointers that I haven't seen in use elsewhere in 20 years. It doesn't ease understanding of the code. Find attached a patch to use the common syntax instead. See Paul Eggert's opinion on this in https://lists.gnu.org/archive/html/bug-gnulib/2020-09/msg00019.html . -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2020-10-10 10:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-26725-132@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@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).