Re: First C Compiler
Yeah, that does catch people out, but there are a lot worse problems running around in all languages (even in C).
Programming languages were never there to insulate you from your own mistakes until very recently (and with any half-decent C compiler, that will stand out a mile the second you compile it). They were there to interface with a computer that does EXACTLY what you tell it to, every single time. It just made that interface a little easier for humans to manage, not take away all possible delusions that a human could possibly be under about their own code.
As someone who uses C99 as the language of my choice, I can tell you that I've made that mistake exactly once personally, spot it in other people's code without the need of a compiler, and haven't used a compiler in the last 15 years that DIDN'T generate warnings about it.
If humans are stupid enough to ignore compiler warnings, they shouldn't even bother with them. Similarly, if a programmer is stupid enough to think that the computer will catch all their mistakes, they should stop programming.
As my tag on a C forum says:
"Compiler warnings are like 'Bridge Out Ahead' warnings."
You can ignore them if you want. I wouldn't recommend it. I haven't yet found a language where it *isn't* possible to shoot yourself in the foot.