From: "Kayvan A. Sylvan" <kayvan@sylvan.com>
To: Kirk <kirkrw@mediaone.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: how can cout be undeclared?
Date: Fri, 08 Feb 2002 14:14:00 -0000 [thread overview]
Message-ID: <20020208221404.GA9530@satyr.sylvan.com> (raw)
In-Reply-To: <02020813570506.01192@truffula.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On Fri, Feb 08, 2002 at 01:57:05PM -0600, Kirk wrote:
> I'm trying to a program ported from linux (redhat7.2 running gcc-2.96RH) to
> freebsd. I have installed gcc-3.0. Most of the compile time errors that I was
> getting while using gcc-2.95 on freebsd have disappeared now that I'm
> compiling with gcc-30. However, there is one that is perplexing me. It is:
>
> tveg.cpp: In member function `void TVeg::dayOut(TDay*)':
> tveg.cpp:428: `cout' undeclared (first use this function)
> tveg.cpp:428: (Each undeclared identifier is reported only once for each
> function it appears in.)....
>
> the whole error output is below.
>
> It is odd that a simple cout (which compiles fine on redhat's 2.96 version)
> is choking here.
>
> Any thoughts?
>
> Thanks in advance,
>
> Kirk
This is correct behavior. gcc-2.X was not quite standard-conforming.
Add a "using std::cout;" statement and all should be well.
---Kayvan
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-08 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 11:50 Kirk
2002-02-08 13:41 ` Frank Geck
2002-02-08 14:14 ` Kayvan A. Sylvan [this message]
2002-02-08 16:12 ` gnu C++ compilation problem Kallol Biswas
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=20020208221404.GA9530@satyr.sylvan.com \
--to=kayvan@sylvan.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kirkrw@mediaone.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).