From: Joe Buck <jbuck@synopsys.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>,
Raja R Harinath <harinath@cs.umn.edu>,
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
mark@codesourcery.com, gcc@gcc.gnu.org,
gdr@integrable-solutions.net
Subject: Re: Converting to ISO C89
Date: Wed, 26 Mar 2003 00:05:00 -0000 [thread overview]
Message-ID: <20030325142528.B7739@synopsys.com> (raw)
In-Reply-To: <87smtbgl65.fsf@egil.codesourcery.com>; from zack@codesourcery.com on Tue, Mar 25, 2003 at 02:01:54PM -0800
Raja R Harinath <harinath@cs.umn.edu> writes:
> >> > Hopefully the ISO C89 changes also make the source C++-safe.
Zack Weinberg <zack@codesourcery.com> writes:
> >> It will not. There is extensive use of identifiers which are C++
> >> keywords, such as 'class' and 'delete'. I do not think your
> >> suggestion is useful enough to warrant changing all of these
> >> identifiers.
Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> writes:
> > Couldn't that be easily worked around with -Dclass=__class or
> > something?
On Tue, Mar 25, 2003 at 02:01:54PM -0800, Zack Weinberg wrote:
> Is this not a cure worse than the disease?
As a "permanent" solution it would be fairly brittle. But for the purpose of
an experiment, to see if any type errors can be found in GCC (due to prototype
mismatches or misuse of enums) it could be worth a shot. It might not work
as well as expected, if some system header optionally defines a class if
__cplusplus is defined.
next prev parent reply other threads:[~2003-03-25 22:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 7:12 Mark Mitchell
2003-03-25 12:12 ` Gabriel Dos Reis
2003-03-25 17:38 ` Mark Mitchell
2003-03-25 18:25 ` Kaveh R. Ghazi
2003-03-25 20:38 ` Raja R Harinath
2003-03-25 21:55 ` Zack Weinberg
2003-03-25 22:02 ` Falk Hueffner
2003-03-25 22:17 ` Zack Weinberg
2003-03-25 22:25 ` Falk Hueffner
2003-03-26 9:19 ` Gabriel Dos Reis
2003-03-26 0:05 ` Joe Buck [this message]
2003-03-26 6:56 ` Zack Weinberg
2003-03-25 22:13 ` Raja R Harinath
2003-03-25 22:23 ` tm_gccmail
2003-03-25 22:26 ` Joe Buck
2003-03-25 22:40 ` Raja R Harinath
2003-03-26 8:49 ` Gabriel Dos Reis
2003-03-26 9:55 ` Zack Weinberg
2003-04-06 2:11 ` Alexandre Oliva
2003-04-06 2:46 ` Zack Weinberg
2003-04-06 2:47 ` Alexandre Oliva
2003-04-06 3:15 ` Kaveh R. Ghazi
2003-04-06 4:40 ` Geoff Keating
2003-04-06 16:23 ` Kaveh R. Ghazi
2003-03-30 12:45 ` Gabriel Dos Reis
2003-03-31 5:17 ` Mark Mitchell
2003-04-03 1:06 ` Zack Weinberg
2003-04-12 17:59 ` Gabriel Dos Reis
2003-04-12 18:06 ` Kaveh R. Ghazi
2003-04-10 15:31 ` Andrew Haley
2003-04-10 16:42 ` Mark Mitchell
2003-04-12 19:32 ` Gabriel Dos Reis
2003-04-14 11:21 ` Mark Mitchell
2003-04-14 12:57 ` Andrew Haley
2003-04-16 10:42 ` Andrew Haley
2003-04-16 17:25 ` Kaveh R. Ghazi
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=20030325142528.B7739@synopsys.com \
--to=jbuck@synopsys.com \
--cc=falk.hueffner@student.uni-tuebingen.de \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=ghazi@caip.rutgers.edu \
--cc=harinath@cs.umn.edu \
--cc=mark@codesourcery.com \
--cc=zack@codesourcery.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).