This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/69782] [6 Regression] defining min() macro causes thousand of lines of error messages
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 12 Feb 2016 18:16:44 +0000
- Subject: [Bug libstdc++/69782] [6 Regression] defining min() macro causes thousand of lines of error messages
- Auto-submitted: auto-generated
- References: <bug-69782-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69782
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #4)
> it can be less than trivial. A fairly easy way to avoid having to deal with
> the problem in libstdc++ is to enclose every call to min and max in public
> libstdc++ headers in parentheses: z = (min)(x, y).
That doesn't help for std::numeric_limits<int>::min()