public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "sds at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/5200] New: regex uses K&R definitions instead of ANSI C
Date: Fri, 19 Oct 2007 15:17:00 -0000	[thread overview]
Message-ID: <20071019151650.5200.sds@gnu.org> (raw)

regcomp.c and regexec.c use old K&R function definitions instead of the ANSI C.
this makes it impossible to compile regex with g++.
glibc regex is used by gnulib 
and thus by dozens of packages that import regex from gnulib.
this makes all those packages uncompilable with g++.
(even when the package is plain C, it is useful to compile it
with c++ every now and then to get a better type checking).
I have patched regcomp.c and regexec.c to compile with g++.
I don't see a way to attach a file though.

-- 
           Summary: regex uses K&R definitions instead of ANSI C
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: drepper at redhat dot com
        ReportedBy: sds at gnu dot org
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5200

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-10-19 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 15:17 sds at gnu dot org [this message]
2007-10-19 15:19 ` [Bug regex/5200] " sds at gnu dot org
2007-10-19 15:20 ` sds at gnu dot org
2007-10-20  3:30 ` drepper at redhat dot com

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=20071019151650.5200.sds@gnu.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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: 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).