On Mon, 24 Sep 2012, Jon Trulson wrote: > A couple of things - Peter was not fond of this commit since he thinks > it wise that we be reminded of these warnings so they will actually be > fixed someday. That said, who knows how long this will take, or > exactly what is involved (openmotif fixes to go along?), etc.
I agree, but it actually prevents me to see other warnings which get hidden between these. > Also, this is a gcc specific option - If we do want to do this (I invite > discussion/opinions from others here), we will want to protect these with > 'HasGcc2ForCplusplus' checks. Good idea, need to check how it goes with the order of imake processing. Yes, my next step is to try compiling a whole tree with clang. clang is partially compatible with GCC (so it will accept this option), but we will need different set of options (for example clang gets really annoying about without -Wno-parentheses). I would probably propose to introduce GCC-specific and clang-specific defaults (or leave it as is for the rest, like SUN Studio etc.). > For myself, I'm all for shutting up compiler warnings, but not if > there is the possibility of hiding real bugs. This warning - please correct me if I am wrong - is more about lost opportunity than bug. The compiler cannot apply aliasing rules if the string were constant. //Marcin ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
