public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Robert Schweikert <rjschwei@cox.net>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: iostream question
Date: Tue, 15 Oct 2002 04:29:00 -0000	[thread overview]
Message-ID: <m3vg44owp4.fsf@soliton.integrable-solutions.net> (raw)
In-Reply-To: Robert Schweikert's message of "Tue, 15 Oct 2002 05:11:45 -0400"

Robert Schweikert <rjschwei@cox.net> writes:

| I am trying to compile a large application with gcc 3.2, (porting from 
| gcc 2.95.2) and am getting errors like this.
| 
| /home/rjschwei/local/include/c++/3.2/backward/iostream.h:35: using
| declaration
|    `ostream' introduced ambiguous type `ostream'

Did your application already declared ostream before #include <iostream.h>?
(I suspect that is the case).  If so, then, you no option but delete
that forward-declaration.

-- Gaby

  reply	other threads:[~2002-10-15  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  3:50 Robert Schweikert
2002-10-15  4:29 ` Gabriel Dos Reis [this message]
2002-10-17  6:51   ` Robert Schweikert
2002-10-17  6:51     ` Phil Edwards

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=m3vg44owp4.fsf@soliton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --cc=rjschwei@cox.net \
    /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).