From: Mike Stump <mrs@apple.com>
To: Chris Garrett <cgarrett@degarrah.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.0.1 - iostream: No such file or dir....
Date: Mon, 08 Aug 2005 04:10:00 -0000 [thread overview]
Message-ID: <61BC60B7-07C2-11DA-A776-003065BDF310@apple.com> (raw)
In-Reply-To: <42F66CCB.6000806@degarrah.com>
On Sunday, August 7, 2005, at 01:19 PM, Chris Garrett wrote:
> 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?
If you want to contribute to the source code of gcc, the compiler, then
those contributions go to gcc. If one is using gcc, those issues go to
gcc-help.
next prev parent reply other threads:[~2005-08-08 4:10 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
2005-08-08 4:10 ` Mike Stump [this message]
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=61BC60B7-07C2-11DA-A776-003065BDF310@apple.com \
--to=mrs@apple.com \
--cc=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).