Re: Ancient history

In article <7xk6kwtb4o.fsf@ruckus.brouhaha.com>,
Paul Rubin <http://phr.cx@NOSPAM.invalid> wrote:
>"Douglas A. Gwyn" <DAGwyn@null.net> writes:
>> That's a vacuous "if". When a programmer codes allocation
>> of some buffer he knows darn well what its bounds are, and
>> can easily use that information to check subsequent access.
>
>The same can be said for just about every other type of bug, and yet
>bugs happen. Was every program you ever wrote 100% bug-free the first
>time you ran it? There's nothing special about that type of bug. If
>your programs can have other types of bugs, it can have that type too.
>All bugs are easy to avoid after the fact.

It is also orthogonal and irrelevant to my point, as I said.

What I was referring to is the fact that nobody knows where the
boundary between defined and undefined behaviour is in how much
certain C constructions use. While it is easy to avoid some of
them, others are almost unavoidable and are widespread throughout
real code.

Regards,
Nick Maclaren.
Received on Thu Sep 29 21:43:55 2005