public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/1220] regex uses old-style definitions that cause g++ to fail
Date: Tue, 06 Sep 2005 18:11:00 -0000 [thread overview]
Message-ID: <20050906181031.12275.qmail@sourceware.org> (raw)
In-Reply-To: <20050820072603.1220.eggert@gnu.org>
------- Additional Comments From drepper at redhat dot com 2005-09-06 18:10 -------
> These days there's no longer any reason for regex to use K&R function
> definition syntax,
Wrong. Using K&R function definitions ensures that the compiler warns about
missing prototypes. This is finer grained than a compiler can achieve this.
It is simply wrong to use g++ to compile regex.c. Period.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://sourceware.org/bugzilla/show_bug.cgi?id=1220
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-09-06 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 7:26 [Bug regex/1220] New: " eggert at gnu dot org
2005-08-20 7:26 ` [Bug regex/1220] " eggert at gnu dot org
2005-08-20 7:28 ` eggert at gnu dot org
2005-08-20 7:32 ` eggert at gnu dot org
2005-08-21 0:25 ` eggert at gnu dot org
2005-08-23 18:28 ` eggert at gnu dot org
2005-08-31 22:43 ` eggert at gnu dot org
2005-09-06 18:04 ` drepper at redhat dot com
2005-09-06 18:11 ` drepper at redhat dot com [this message]
2006-04-19 17:43 ` bruno at clisp dot org
2006-04-19 17:44 ` bruno at clisp dot org
2006-04-25 18:01 ` 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=20050906181031.12275.qmail@sourceware.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).