There are a fair few of these in c++ builds which tend to obscure some
of the actually useful warnings. Antoine noticed it a while ago, Landry
noticed it recently, I see it from time to time..
Any suggestions other than not using -pedantic? (Actually I think
I have seen this without -pedantic too somewhere but I forget where).
Is this just a silly warning or is there actually a problem with the
headers?
This example is from chopping down a file from converters/wv2 (which
is itself a relatively small example) until the warning no longer
occurs then going back one step.
$ cat > a.c
#include <string>
^D
$ c++ -pedantic -c a.c
In file included from /usr/include/g++/memory:60,
from /usr/include/g++/string:48,
from a.c:1:
/usr/include/g++/limits: In static member function 'static char
std::numeric_limits<char>::min()':
/usr/include/g++/limits:375: warning: overflow in implicit constant conversion
/usr/include/g++/limits: In static member function 'static wchar_t
std::numeric_limits<wchar_t>::max()':
/usr/include/g++/limits:530: warning: overflow in implicit constant conversion
