public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/18442] New: re_syntax_options namespace
Date: Thu, 21 May 2015 15:31:00 -0000 [thread overview]
Message-ID: <bug-18442-132@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18442
Bug ID: 18442
Summary: re_syntax_options namespace
Product: glibc
Version: 2.21
Status: NEW
Severity: normal
Priority: P2
Component: regex
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Use of regcomp (POSIX) brings in references to re_syntax_options (non-POSIX);
re_comp (UNIX98 and older legacy) actually uses re_syntax_options (not in those
standards) rather than just being in the same .o file. (As this is a data
symbol that users can set directly, fixing this is harder than simply using an
implementation-namespace name with a weak alias as can be done for functions.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-05-21 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 15:31 jsm28 at gcc dot gnu.org [this message]
2015-05-21 16:25 ` [Bug regex/18442] " cvs-commit at gcc dot gnu.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=bug-18442-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: link
Be 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).