From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org
Subject: Re: [ARI] Add "bzero"
Date: Wed, 27 May 2009 18:15:00 -0000 [thread overview]
Message-ID: <m3k542v2e5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090521002704.GG16152@adacore.com> (Joel Brobecker's message of "Wed\, 20 May 2009 17\:27\:04 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Tom> For this specific case, and some others like it, perhaps using #pragma
Tom> poison would be better. That would result in a compile time error,
Tom> rather than a report on a web page.
Joel> I really liked the idea and gave it a quick try, but I don't know
Joel> how to make it work. I thought I would put the pragma at the end of
Joel> defs.h, since defs.h is always included. But defs.h is also always
Joel> the first file to be included, and so any #include that follows it
Joel> which references any of the poisoned identifier will cause an error.
Joel> Do you see another way?
Nope. In gcc I think the possibly-offending system headers are all
included in a single header file ("system.h"), and then the poisoning
is done at the end of that file.
Tom
next prev parent reply other threads:[~2009-05-27 18:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 6:38 [RFA] Fix memory leak in gdbserver Doug Evans
2009-04-30 9:28 ` Pedro Alves
2009-05-06 8:50 ` Build failure for x86_64-pc-mingw32 target Kai Tietz
2009-05-06 9:05 ` Hui Zhu
2009-05-06 9:37 ` Pedro Alves
2009-05-06 10:46 ` Hui Zhu
2009-05-06 11:20 ` Hui Zhu
2009-05-06 11:36 ` Kai Tietz
2009-05-06 16:03 ` [ARI] Add "bzero" (was: "Re: Build failure for x86_64-pc-mingw32 target") Joel Brobecker
2009-05-06 16:53 ` Joel Brobecker
2009-05-06 18:11 ` Eli Zaretskii
2009-05-06 18:37 ` Joel Brobecker
2009-05-18 19:24 ` [ARI] Add "bzero" Tom Tromey
2009-05-20 5:19 ` Joel Brobecker
2009-05-21 0:27 ` Joel Brobecker
2009-05-27 18:15 ` Tom Tromey [this message]
2009-05-06 10:19 ` Build failure for x86_64-pc-mingw32 target Mark Kettenis
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=m3k542v2e5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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