public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Matt Austern <austern@apple.com>
Cc: Ji Li <liji@jlab.org>, gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: STL with gcc3
Date: Wed, 17 Jul 2002 14:15:00 -0000	[thread overview]
Message-ID: <20020717171507.A20179@disaster.basement.lan> (raw)
In-Reply-To: <953DCC54-99B4-11D6-A92C-00039390D9E0@apple.com>; from austern@apple.com on Wed, Jul 17, 2002 at 11:39:53AM -0700

On Wed, Jul 17, 2002 at 11:39:53AM -0700, Matt Austern wrote:
> On Wednesday, July 17, 2002, at 11:35 AM, Ji Li wrote:
> >
> > 	I believe there must be a way to make gcc-3.0.4 backward
> > compatable but just could find it. Would you please point the way for 
> > me?
> 
> You really don't want to do that.  The standard says that everything
> in the Standard Library is supposed to be in namespace std.  Other
> compilers have conformed to the standard for years.  You should
> change your code, for portability if for no other reason.

Matt is correct; your code is not C++.  To aid in making the transition, gcc
3.x lets you include <backward/iostream.h>.  But there is no comparable header
for <string>, since there was never really a pre-standard string class.  So
you'll have to edit your code anyway; may as well fix the I/O names as well.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2002-07-17 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 11:35 Ji Li
2002-07-17 11:40 ` Matt Austern
2002-07-17 14:15   ` Phil Edwards [this message]
2002-07-17 14:56     ` Ji Li
2002-07-17 15:01       ` Gabriel Dos Reis
2002-07-17 14:31 ` Joe Buck

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=20020717171507.A20179@disaster.basement.lan \
    --to=phil@jaj.com \
    --cc=austern@apple.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=liji@jlab.org \
    /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).