From: Raja R Harinath <harinath@cs.umn.edu>
To: Zack Weinberg <zack@codesourcery.com>
Cc: "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: Tue, 25 Mar 2003 22:13:00 -0000 [thread overview]
Message-ID: <d9llz36rdq.fsf@bose.cs.umn.edu> (raw)
In-Reply-To: <873clbi0p6.fsf@egil.codesourcery.com> (Zack Weinberg's message of "Tue, 25 Mar 2003 13:41:09 -0800")
Hi,
Zack Weinberg <zack@codesourcery.com> writes:
> Raja R Harinath <harinath@cs.umn.edu> writes:
>
>> Hopefully the ISO C89 changes also make the source C++-safe.
>
> 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.
Fair enough.
> What might be useful is an optional mode for the C compiler in which
> function names get mangled as they would be in C++. That would have
> the effect of type-checking procedure calls across translation units
> at link time. To avoid mangling calls into libc it would have to be
> switchable within each translation unit -- one plausible approach is
> to recognize extern "C" and extern "C++" in C, another is #pragma.
I was thinking more about optimization: ensure that there's no
abstraction penalty for using a C++ compiler on C code, and that both
the C and C++ compilers exploit the same optimization opportunities.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
next prev parent reply other threads:[~2003-03-25 21:57 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
2003-03-26 6:56 ` Zack Weinberg
2003-03-25 22:13 ` Raja R Harinath [this message]
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=d9llz36rdq.fsf@bose.cs.umn.edu \
--to=harinath@cs.umn.edu \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=ghazi@caip.rutgers.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).