public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@codesourcery.com>
To: Ji Li <liji@jlab.org>
Cc: Phil Edwards <phil@jaj.com>, Matt Austern <austern@apple.com>,
	gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: STL with gcc3
Date: Wed, 17 Jul 2002 15:01:00 -0000	[thread overview]
Message-ID: <m3y9cavwur.fsf@merlin.nerim.net> (raw)
In-Reply-To: Ji Li's message of "Wed, 17 Jul 2002 17:56:47 -0400 (EDT)"

Ji Li <liji@jlab.org> writes:

| Hi,
| 
| 	Yes I get the idea. The question is the real code that I am
| dealing with is far more comlex than the example I gave here. Ok, I will
| try to change the code. Thanks to you all for your help.

As a transition, you might want to start with a "using namespace std;" right
after the includes.

-- Gaby

  reply	other threads:[~2002-07-17 22:01 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
2002-07-17 14:56     ` Ji Li
2002-07-17 15:01       ` Gabriel Dos Reis [this message]
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=m3y9cavwur.fsf@merlin.nerim.net \
    --to=gdr@codesourcery.com \
    --cc=austern@apple.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=liji@jlab.org \
    --cc=phil@jaj.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).