public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sletter@slb.com To: gcc-gnats@gcc.gnu.org Subject: c++/9923: Include file behaves differently Date: Mon, 03 Mar 2003 17:56:00 -0000 [thread overview] Message-ID: <20030303174712.15106.qmail@sources.redhat.com> (raw) >Number: 9923 >Category: c++ >Synopsis: Include file behaves differently >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Mar 03 17:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: sletter@slb.com >Release: 3.0.2 >Organization: >Environment: Red Hat Linux 7.2. >Description: #include "/usr/include/unistd.h" extern "C" int access(const char *, int); Compiling above causes an error (g++ -c foo.c) while #include <unistd.h> extern "C" int access(const char *, int); does not. For some reason the C++ front end treats quoted includes differently than bracketed ones. >How-To-Repeat: compile the above code snippets and the error should present itself. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-03 17:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 17:56 sletter [this message] 2003-03-03 18:16 nathan 2003-03-03 19:06 Steve Letter 2003-03-03 19:36 Andreas Schwab 2003-03-03 20:46 Nathan Sidwell
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=20030303174712.15106.qmail@sources.redhat.com \ --to=sletter@slb.com \ --cc=gcc-gnats@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).