From: Joe Buck <jbuck@synopsys.com>
To: Jim Wilson <wilson@specifixinc.com>
Cc: The Penguine <the_penguine@hotmail.com>, gcc@gcc.gnu.org
Subject: Re: Which gcc is the most stable today ?
Date: Wed, 10 Dec 2003 19:27:00 -0000 [thread overview]
Message-ID: <20031210093711.B17472@synopsys.com> (raw)
In-Reply-To: <3FD6B641.5050805@specifixinc.com>; from wilson@specifixinc.com on Tue, Dec 09, 2003 at 09:59:29PM -0800
On Tue, Dec 09, 2003 at 09:59:29PM -0800, Jim Wilson wrote:
> The best compiler to use is often the compiler that came with the OS,
> which would be the Red Hat gcc-2.96 in your case.
For C, this is true (the OS's compiler is fine); however, for C++, I would
strongly urge that no 2.x release be used for new development. Lack of a
proper std namespace is a substantial issue, and you'll pay substantial
costs down the road if you proceed to whack out a lot of nonstandard,
broken code that 2.96 will accept but no other compiler will.
2.95.x and Red Hat's 2.96 do have a mechanism to fake the existence of
a std namespace, which allows many standard programs to compile. This
means that it can work to develop code that runs on 2.96, but you also
need to be sure that it builds with a proper C++ compiler.
prev parent reply other threads:[~2003-12-10 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 9:46 The Penguine
2003-12-09 15:43 ` Kelley Cook
2003-12-10 6:04 ` Jim Wilson
2003-12-10 19:27 ` Joe Buck [this message]
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=20031210093711.B17472@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=the_penguine@hotmail.com \
--cc=wilson@specifixinc.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).