public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: y2bismil@engmail.uwaterloo.ca
To: cygwin@cygwin.com
Subject: Re: gcc and iostream
Date: Fri, 31 Oct 2003 17:00:00 -0000	[thread overview]
Message-ID: <1067617166.3fa28b8ecc072@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <1067616628.3fa2897461121@www.nexusmail.uwaterloo.ca>

Ah, okay,

running just the preprocessor on the file, This is what I get:

Nothing weird is being pulled in from other directories.  The iostream
references are as follows:

# 1 "/usr/include/c++/3.3.1/iostream" 1 3
# 43 "/usr/include/c++/3.3.1/iostream" 3
..
# 1 "/usr/include/c++/3.3.1/backward/iomanip.h" 1 3
# 31 "/usr/include/c++/3.3.1/backward/iomanip.h" 3
# 1 "/usr/include/c++/3.3.1/backward/backward_warning.h" 1 3
# 32 "/usr/include/c++/3.3.1/backward/iomanip.h" 2 3
# 1 "/usr/include/c++/3.3.1/backward/iostream.h" 1 3
# 34 "/usr/include/c++/3.3.1/backward/iostream.h" 3

This has me a bit concerned, and I'm looking at it.  Any ideas?

Thanks 

Yamin


Quoting y2bismil@engmail.uwaterloo.ca:

> Hi all,
> 
> Okay, I've replaced the using namespace std with std:: for each call to
> cout/cin.  The error I got was interesting.  It seems cout is not declared
> in
> namepace std.
> 
> error: `cout' undeclared in namespace `std'
> 
> Obviously something is up.  If anyone can think of anything, let me know. 
> The
> only lead I'm tracing now is if the Tornado headers are somehow being pulled
> in.
> 
> Thanks all,
> 
> Yamin
> 
> 
> 
> ----------------------------------------
> This mail sent through www.mywaterloo.ca
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 




----------------------------------------
This mail sent through www.mywaterloo.ca

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-10-31 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 22:35 y2bismil
2003-10-31  2:26 ` Brian Ford
2003-10-31  7:20   ` Gary R. Van Sickle
2003-10-31 10:00 ` Gerrit P. Haase
2003-10-31 16:22   ` y2bismil
2003-10-31 17:00     ` y2bismil [this message]
2003-10-31 18:13       ` gcc and iostream - final issue y2bismil
2003-10-31 18:39         ` Christopher Faylor
2003-10-31 21:07         ` Brian Ford
2003-10-31 21:34           ` y2bismil
2003-10-31 22:05             ` gcc and iostream - resolved y2bismil
2003-10-31 22:48               ` Brian Ford
2003-10-31 22:24             ` gcc and iostream - final issue Brian Ford
2003-10-30 22:41 gcc and iostream Timothy C Prince

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=1067617166.3fa28b8ecc072@www.nexusmail.uwaterloo.ca \
    --to=y2bismil@engmail.uwaterloo.ca \
    --cc=cygwin@cygwin.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).