From: Robert Schweikert <rjschwei@cox.net>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: iostream question
Date: Thu, 17 Oct 2002 06:51:00 -0000 [thread overview]
Message-ID: <3DAE09E5.2040002@cox.net> (raw)
In-Reply-To: <m3vg44owp4.fsf@soliton.integrable-solutions.net>
OK,
Are you saying I can no longer forward declare an ostream?
That would mean that for a declaration like so
ostream& operator<< (ostream&, const myClass);
I have to include the iostream header file in my header file. That seems odd. There's got to be a better way.
Robert
Gabriel Dos Reis wrote:
>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
>
>
>
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
rjschwei@cox.net LINUX
next prev parent reply other threads:[~2002-10-17 0:52 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
2002-10-17 6:51 ` Robert Schweikert [this message]
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=3DAE09E5.2040002@cox.net \
--to=rjschwei@cox.net \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.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).