Bug#343898: fix for unreadable error messages in g++ when #define'ing min or max

2007-09-16 Thread Matthias Klose
tag 343898 + wontfix tag 343898 + moreinfo severity 343898 minor thanks > will you update the patch? no feedback, and afaics not forwarded upstream -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#343898: fix for unreadable error messages in g++ when #define'ing min or max

2006-07-08 Thread Matthias Klose
will you update the patch? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#343898: fix for unreadable error messages in g++ when #define'ing min or max

2006-03-04 Thread Falk Hueffner
Hi, the standard says: A translation unit that includes a header shall not contain any macros that define names declared or defined in that header. So it's not generally disallowed to #define min/max, but rather there should be only exactly two places checking for this, namely and . The err

Bug#343898: fix for unreadable error messages in g++ when #define'ing min or max

2005-12-18 Thread Rudi
Package: libstdc++6-4.0-dev Version: 4.0.2-5 Tags: patch Good day, It seems there is an old and thorny issue that has addled my mind for years. It relates to the changing rules in C++ regarding max and min; in early versions, it was perfectly legal to #define max or min as you please, and indeed