Lit. Buffer overruns 1728

Some of the most dangerous coders are the ones who think so. Just look at the code posted in this thread, like that toupper program that was supposed to be an example of a bug-free program but only worked on text as defined by the C language spec. In particular, look at all the tidbits of information you learned in the aftermath, for example that the Windows piping mechanism does not halt on a 0x1A. That's a "thing or two" you need to know in order to write working code. Me, I didn't know how Windows piping behaves either. I never use it. Gurus are called gurus for a reason: true encyclopedic knowledge of a system or even a PL is not common, even among those who think they have it. Well, in contrast, you say things like, "don't ship until you're sure the code is bug-free." Most coders can not choose their company ship dates, and do not have an inexhaustible amount of time. You might be working insane hours just to meet the ship date with software that doesn't crash on typical inputs. In this kind of environment, it is not pessimistic to buttume that you won't get all the bugs out. --Xcott