Re:Re: C as used/implemented in practice
by GFK_of_xmaspast on Monday July 13, 2015 @09:57PM
(#9882398)
If N is unsigned, clang++ (and I think g++) will warn about signed/unsigned comparison, but sometimes you do want signed loop indices.
[ Parent
| on HN ]
Microsoft's compiler has been ALL OVER THIS for 20 years.
Nothing says "buggy port of Linux app to Windows" faster than "#pragma warning (disable: 4018)".
Clang is catching up. GCC doesn't seem to care as much. Given all the bitching about undefined behavior you'd think they'd up the warnings.
Compilers are programs too, y'know. We can define (and gasp, re-define) behavior.
Re:Re: C as used/implemented in practice
by GFK_of_xmaspast on Tuesday July 14, 2015 @09:58PM
(#9889291)
Well, in fairness and generality nothing says buggy like "disabled warnings".
(and you know you're in trouble when you start looking at a new codebase and see a "-fpermissive" in there)
Totally agree with more warnings being needed, I understand that exploiting UB is needed for optimization, but I don't buy the 'well we can't warn about every case, so we won't warn about any' reasoning.