Re: A way to prevent buffer overflow exploits?

On 16 Aug 1998 22:42:57 -0400, khays@sequent.com (Kirk Hays) wrote:


>>IMHO, if this is a problem for your organization, it's a sign that
>>your hiring practices, and not your programming tools, are at fault.
>
>Oh, my.
>
>So the programmers you hire never have a bad day, an "off by one"
>error, program on a Friday afternoon, fight with their spouses, lack
>experience, misuse a macro, get bit by a bug in a compiler, or have to
>maintain someone else's crufty old code?


I didn't mean that to sound as asinine as it obviously did. I juggle
chainsaws for a living and routinely cut my own arms off, too.


What I really meant was that it often seems that more bad software
engineering results from reasoning along the lines of "I don't need
to check for [condition] because [condition] will never occur" than
from innocent programmer error, and that past a certain point,
built-in language safeguards tend to encourage that sort of reasoning.
That's all.


--Eric
--

Return to the comp.compilers page.
Search the comp.compilers archives again.