From: Phil Edwards <phil@jaj.com>
To: yabada badoo <yabadabadoo123@hotmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Convergence of GCC - slightly off topic
Date: Wed, 02 Oct 2002 19:44:00 -0000 [thread overview]
Message-ID: <20021002215854.A15251@disaster.jaj.com> (raw)
In-Reply-To: <F48zjx4NOPk0O5SjMKt00002904@hotmail.com>; from yabadabadoo123@hotmail.com on Wed, Oct 02, 2002 at 06:47:28PM +0000
On Wed, Oct 02, 2002 at 06:47:28PM +0000, yabada badoo wrote:
> Not wanting to start any flames, but I was
> wondering what is the experts take on the
> likelyhood of convergence of the various
> versions of gcc in the varous linux distributions,
> now that 3.2 is getting consistent positive appraise.
One of the goals of 3.2 was precisely that. Whether the distros do so is
up to them.
> I was hoping to get feedback from seasoned (battered
> battle faces :-) c and c++ folks that are more seasoned in dealing with
> sitiations that might expose some of the more thornier aspects of 3.2 with
> respect to the other (older) gcc versions shipped with various linux
> distros.
The key point is in C++. Every release of GCC 3.x has been more conformant
to the ISO C++ standard than the release before it. Programs which predate
the standard may not actually be legal C++ code anymore.
More info on http://gcc.gnu.org/bugs.html#known
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next prev parent reply other threads:[~2002-10-03 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 13:09 yabada badoo
2002-10-02 19:30 ` kwall
2002-10-02 19:44 ` Phil Edwards [this message]
2002-10-02 20:00 ` Hans-Peter Nilsson
2002-10-03 16:34 ` Joe Buck
2002-10-04 8:46 ` David O'Brien
2002-10-02 14:50 Robert Dewar
2002-10-03 12:18 Joe Buck
2002-10-03 14:38 ` Matt Austern
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=20021002215854.A15251@disaster.jaj.com \
--to=phil@jaj.com \
--cc=gcc@gcc.gnu.org \
--cc=yabadabadoo123@hotmail.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).