public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/1236] New: regex.h violates POSIX name space rules in several places Date: Wed, 24 Aug 2005 22:21:00 -0000 [thread overview] Message-ID: <20050824222100.1236.eggert@gnu.org> (raw) I noticed quite a few violations of POSIX namespace rules in regex.h, and wrote a patch to fix them all. POSIX says that regex.h's extensions must start with re_ or rm_ or end with _t, or be macros that start with REG_. It also says that users can undef the REG_ macros without breaking anything. libc regex.h violates these rules in many places. The attached patch fixes regex.h so that it obeys the POSIX name space rules if the appropriate feature-test macros are defined. There is no change in the usual case. The ABI is not affected. -- Summary: regex.h violates POSIX name space rules in several places Product: glibc Version: 2.3.5 Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: gotom at debian dot or dot jp ReportedBy: eggert at gnu dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com OtherBugsDependingO 1233 nThis: http://sources.redhat.com/bugzilla/show_bug.cgi?id=1236 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-08-24 22:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-24 22:21 eggert at gnu dot org [this message] 2005-08-24 22:21 ` [Bug regex/1236] " eggert at gnu dot org 2005-08-24 22:23 ` eggert at gnu dot org 2005-08-24 23:08 ` eggert at gnu dot org 2005-08-24 23:21 ` eggert at gnu dot org 2005-09-06 20:03 ` drepper at redhat dot com 2006-04-11 6:58 ` eggert at gnu dot org 2006-04-11 6:58 ` eggert at gnu dot org 2006-04-11 7:06 ` eggert at gnu dot org 2010-09-02 14:42 ` schwab at linux-m68k dot org
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=20050824222100.1236.eggert@gnu.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs-regex@sources.redhat.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: 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).