public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7861: Finds executables instead of standard headers? Date: Sun, 23 Feb 2003 22:16:00 -0000 [thread overview] Message-ID: <20030223221600.10357.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7861; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Paul <paulf.johnson@ukonline.co.uk> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, paulf.johnson@ukonline.co.uk?Subject Subject: Re: c++/7861: Finds executables instead of standard headers? Date: Sun, 23 Feb 2003 14:06:31 -0800 Paul <paulf.johnson@ukonline.co.uk> writes: > g++ test.cpp -o string > Compiles fine. > > Change "Paul" to "Phil" (say), recompile and watch the fireworks! Unable to reproduce this - $ cat > test.cc #include <string> #include <iostream> using namespace std; int main() { string hi = "Paul"; cout << "Hello " << hi << endl; } $ g++ test.cc -o string ; echo $? 0 $ g++ test.cc -o string ; echo $? 0 I suspect you neglected to mention that you had -I. on your command line, which is specifically asking for fireworks under these conditions. It would be sensible for cpplib to detect '\177ELF' at the beginning of a file and abandon processing it, so as to avoid flooding the user's terminal with unhelpful error messages. (That string cannot appear at the beginning of a well-formed C/C++ source file.) But it would still be an error. zw
next reply other threads:[~2003-02-23 22:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-23 22:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 1:13 bangerth 2003-02-24 21:26 Zack Weinberg 2003-02-23 22:16 Paul 2003-02-23 21:56 Paul 2003-02-23 21:50 neroden
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=20030223221600.10357.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).