From: Mark Mitchell <mark@codesourcery.com>
To: pthomas@suse.de
Cc: gcc@gcc.gnu.org
Subject: Re: cp/errfn.c
Date: Thu, 06 Jul 2000 22:34:00 -0000 [thread overview]
Message-ID: <20000706223425Q.mitchell@codesourcery.com> (raw)
In-Reply-To: <20000707060630.B25403@Jeffreys.suse.de>
>>>>> "Philipp" == Philipp Thomas <pthomas@suse.de> writes:
Philipp> Mark,
Philipp> errfn.c uses K&R funtion definitions. As it's allways
Philipp> compiled by gcc, I'd say there is no need to do
Philipp> so. Equally so for using VPARAMS.
In general, we've tried to avoid making code in the C++ front-end
impossible to compile with other compilers. We haven't tried too hard
to make sure in can be compiled with other compilers -- but we've
tried not to do obviously unfriendly things. The reason is that code
tends to migrate from one place in the compiler to another. And
errfns.c is code that is likely to end up more widely shared than it
presently is.
Does that make sense?
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2000-07-06 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 21:06 cp/errfn.c Philipp Thomas
2000-07-06 22:34 ` Mark Mitchell [this message]
2000-07-07 5:53 ` cp/errfn.c Philipp Thomas
-- strict thread matches above, loose matches on Subject: below --
1998-02-02 19:07 cp/errfn.c Mike Stump
1998-02-02 15:13 cp/errfn.c John Carr
1998-02-06 0:57 ` cp/errfn.c Jeffrey A Law
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=20000706223425Q.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=pthomas@suse.de \
/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).