public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/9923: Include file behaves differently
@ 2003-03-03 20:46 Nathan Sidwell
0 siblings, 0 replies; 5+ messages in thread
From: Nathan Sidwell @ 2003-03-03 20:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c++/9923; it has been noted by GNATS.
From: Nathan Sidwell <nathan@codesourcery.com>
To: Steve Letter <letter@austin.apc.slb.com>
Cc: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, sletter@slb.com, gcc-gnats@gcc.gnu.org
Subject: Re: c++/9923: Include file behaves differently
Date: Mon, 03 Mar 2003 20:44:25 +0000
Steve Letter wrote:
> Could you please explain why it isn't a bug? It IS breaking a bunch of
> our code. We have to "wrap" the system header, so we have our own (that
> includes the "real" header).
>
> To help me work around this (not a bug) feature, could you explain (a
> little ) what happens to cause this (not a bug) behavior?
read the manual about fixincludes and #include_next
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
The voices in my head said this was stupid too
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c++/9923: Include file behaves differently
@ 2003-03-03 19:36 Andreas Schwab
0 siblings, 0 replies; 5+ messages in thread
From: Andreas Schwab @ 2003-03-03 19:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
The following reply was made to PR c++/9923; it has been noted by GNATS.
From: Andreas Schwab <schwab@suse.de>
To: Steve Letter <letter@austin.apc.slb.com>
Cc: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, sletter@slb.com, gcc-gnats@gcc.gnu.org
Subject: Re: c++/9923: Include file behaves differently
Date: Mon, 03 Mar 2003 20:26:51 +0100
Steve Letter <letter@austin.apc.slb.com> writes:
|> Could you please explain why it isn't a bug? It IS breaking a bunch of
|> our code. We have to "wrap" the system header, so we have our own (that
|> includes the "real" header).
Name the wrappers differently.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c++/9923: Include file behaves differently
@ 2003-03-03 19:06 Steve Letter
0 siblings, 0 replies; 5+ messages in thread
From: Steve Letter @ 2003-03-03 19:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c++/9923; it has been noted by GNATS.
From: Steve Letter <letter@austin.apc.slb.com>
To: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, sletter@slb.com, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/9923: Include file behaves differently
Date: Mon, 03 Mar 2003 12:52:17 -0600
Could you please explain why it isn't a bug? It IS breaking a bunch of
our code. We have to "wrap" the system header, so we have our own (that
includes the "real" header).
To help me work around this (not a bug) feature, could you explain (a
little ) what happens to cause this (not a bug) behavior?
your solution of not doing it isn't practical in this case. Thanks.
On Mon, 2003-03-03 at 12:16, nathan@gcc.gnu.org wrote:
> Synopsis: Include file behaves differently
>
> State-Changed-From-To: open->closed
> State-Changed-By: nathan
> State-Changed-When: Mon Mar 3 18:16:25 2003
> State-Changed-Why:
> not a bug. Like the doctor said - 'don't do that then'
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9923
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: c++/9923: Include file behaves differently
@ 2003-03-03 18:16 nathan
0 siblings, 0 replies; 5+ messages in thread
From: nathan @ 2003-03-03 18:16 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, sletter
Synopsis: Include file behaves differently
State-Changed-From-To: open->closed
State-Changed-By: nathan
State-Changed-When: Mon Mar 3 18:16:25 2003
State-Changed-Why:
not a bug. Like the doctor said - 'don't do that then'
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9923
^ permalink raw reply [flat|nested] 5+ messages in thread
* c++/9923: Include file behaves differently
@ 2003-03-03 17:56 sletter
0 siblings, 0 replies; 5+ messages in thread
From: sletter @ 2003-03-03 17:56 UTC (permalink / raw)
To: gcc-gnats
>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:
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-03-03 20:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-03 20:46 c++/9923: Include file behaves differently Nathan Sidwell
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 19:36 Andreas Schwab
2003-03-03 19:06 Steve Letter
2003-03-03 18:16 nathan
2003-03-03 17:56 sletter
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).