Julian Foad writes: > Andy queried why we aren't using the GCC option "-Wall". > > I've been compiling for a few weeks now with extra GCC warnings > enabled, to see whether it will help with portability issues or > just be a nuisance. I used these options: > > -Wall -pedantic -Wpointer-arith
Thanks. [snip] > Here are all of the warnings from SimGear (about a week old): > > Making all in xml > In file included from xmltok.c:260: xmltok*.c are included directly from Expat, so we probably don't want to fool with these, at least unless we're willing to fork. > Making all in misc > props.cxx: In method `SGPropertyNode::hash_table::~hash_table()': > props.cxx:1980: warning: comparison between signed and unsigned > > [This is mostly harmless but should be fixed (and can be fixed easily and >correctly).] I've fixed it in my local copy, and will check into CVS as soon as I have a chance to check it. > Making all in io > In file included from lowlevel.cxx:28: > lowlevel.hxx:40: warning: ANSI C++ does not support `long long' > lowlevel.hxx:41: warning: ANSI C++ does not support `long long' > lowlevel.hxx: In function `void sgEndianSwap(uint64 *)': > lowlevel.hxx:151: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:152: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:153: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:154: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:155: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:156: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:157: warning: ANSI C++ forbids long long integer constants > lowlevel.hxx:158: warning: ANSI C++ forbids long long integer constants > > [Is there a more standard way to get a 64-bit integer, like > "int64_t" in <stdint.h> of ANSI C'99? This warning only appears > when "-pedantic" is used, and can be inhibited with -Wno-long-long. > This bunch of warnings came out four times.] Unfortunately, stdint.h uses long long as well, so it will probably also trigger the warning. Ouch. Any suggestions? I'll leave the others to the appropriate coders. Thanks, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
