From: Chris Garrett <cgarrett@degarrah.com>
To: gcc@gcc.gnu.org
Subject: Re: GCC 4.0.1 - iostream: No such file or dir....
Date: Sun, 07 Aug 2005 20:19:00 -0000 [thread overview]
Message-ID: <42F66CCB.6000806@degarrah.com> (raw)
In-Reply-To: <1243.24.126.76.52.1123343363.squirrel@webmail3.pair.com>
dank@kegel.com wrote:
>Chris Garrett <cgarrett@degarrah.com> wrote:
>
>
>>main.cpp:5: error: 'cout' was not declared in this scope
>>
>>
>This question should have been sent to gcc-help, not here.
>
>
Sorry about this. What criteria is there for posting to gcc vs gcc-help?
>But as long as I'm answering:
>
>It's std::cout now, according to the C++ standard.
>If you want to compile old code that wasn't aware of std,
>you can stick
> using namespace std;
>at the top.
>
>
>
Thanks for answering, I forgot to mention that I did try adding the
namespace prefix and also the "using" statement and I get the same error.
Thank you
Chris
next prev parent reply other threads:[~2005-08-07 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 15:49 dank
2005-08-07 20:19 ` Chris Garrett [this message]
2005-08-08 4:10 ` Mike Stump
2005-08-08 17:40 ` Chris Garrett
-- strict thread matches above, loose matches on Subject: below --
2005-08-06 4:52 Chris Garrett
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=42F66CCB.6000806@degarrah.com \
--to=cgarrett@degarrah.com \
--cc=gcc@gcc.gnu.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).