public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/49386] #undef min/max is dependent on order if #include Date: Sun, 26 Jun 2011 22:40:00 -0000 [thread overview] Message-ID: <bug-49386-4-rj8wIX3FPG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49386-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49386 Paolo Carlini <paolo.carlini at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paolo.carlini at oracle dot | |com --- Comment #12 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-06-26 22:39:20 UTC --- Dave, do you have an opinion about this issue? I'm tempted to close it as WONTFIX, frankly, I don't think we want to go beyond the #undefs we already have got in c++config, I would even do less (but probably code is already relying on that),
next prev parent reply other threads:[~2011-06-26 22:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-13 7:23 [Bug libstdc++/49386] New: " gintensubaru at gmail dot com 2011-06-13 7:55 ` [Bug libstdc++/49386] " chris at bubblescope dot net 2011-06-13 8:09 ` gintensubaru at gmail dot com 2011-06-13 8:16 ` chris at bubblescope dot net 2011-06-13 8:29 ` gintensubaru at gmail dot com 2011-06-13 9:26 ` paolo.carlini at oracle dot com 2011-06-13 9:29 ` paolo.carlini at oracle dot com 2011-06-13 9:35 ` paolo.carlini at oracle dot com 2011-06-13 9:44 ` paolo.carlini at oracle dot com 2011-06-13 10:58 ` jakub at gcc dot gnu.org 2011-06-13 11:37 ` paolo.carlini at oracle dot com 2011-06-13 11:55 ` paolo.carlini at oracle dot com 2011-06-26 22:40 ` paolo.carlini at oracle dot com [this message] 2012-01-04 10:11 ` paolo.carlini at oracle dot com
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=bug-49386-4-rj8wIX3FPG@http.gcc.gnu.org/bugzilla/ \ --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).