public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stl at caltech dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/12258] -Wold-style-cast triggers on casts in macros from system headers Date: Sat, 13 Mar 2004 02:11:00 -0000 [thread overview] Message-ID: <20040313021134.15176.qmail@sources.redhat.com> (raw) In-Reply-To: <20030912015846.12258.stl@caltech.edu> ------- Additional Comments From stl at caltech dot edu 2004-03-13 02:11 ------- My current workaround is similar to what Kai Henningsen proposed: I have my own const constants for #define'd constants, as well as my own functions for #define'd macros (e.g. FD_SET), in a separate header which I then mark as a GCC system header. This produces warning-free code. It's a dirty hack, though. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12258
next prev parent reply other threads:[~2004-03-13 2:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-09-12 1:58 [Bug c++/12258] New: " stl at caltech dot edu 2003-09-17 5:23 ` [Bug preprocessor/12258] " pinskia at gcc dot gnu dot org 2004-03-13 2:11 ` stl at caltech dot edu [this message] [not found] <bug-12258-4@http.gcc.gnu.org/bugzilla/> 2010-11-23 18:18 ` hjl at gcc dot gnu.org 2021-12-29 23:40 ` carlosgalvezp at gmail dot com 2021-12-30 10:30 ` redi at gcc dot gnu.org
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=20040313021134.15176.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).