Re: [tlug] using rusage: "better safe than sorry" programming by default

["Josh Glover" <jmglov@example.com>]

2008/6/22 jep200404 <jep200404@example.com>:

> Josh wrote:
>
>> 2008/6/22 Curt Sampson <cjs@example.com>:
>>
>> > But then again, if you're in a "better safe than sorry" mode....
>>
>> Shouldn't this be the default position of systems programmers?
>
> Why limit it to _systems_ programmers?

Of course. But my point is that defensive programming is even *more*
vital for systems programmers, as they tend to write complicated,
low-level stuff where forgetting to check a return value or using a
syscall that does not play well with signals could have serious
implications.

When I worked at TFCC in Columbus, my forgetting to check a return
code and not handling it gracefully could result in people *dying*.
That tends to teach good programming habits.

-- 
Cheers,
Josh