Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: "Malcolm McLean" <regniztar@xxxxxxxxxxxxxx>
- Date: Wed, 17 Oct 2007 21:09:31 +0100
"Ben Bacarisse" <ben.usenet@xxxxxxxxx> wrote in message
You've got to have a degree of knowledge about the fruit industry before you can say whether the box is dangerous.[Interview]er: "Here is a wooden box to keep apples in.
What security flaws can you find in it?"
[Interview]ee (after a careful examination):
"There aren't any."
er: "You failed the interview. You didn't consider the risk
of someone breaking someone's skull with it."
ee: "That's not a proper use of the box! The box is
perfectly safe if used properly."
er: "That wouldn't help."
Analogies are slippery things. I could have gone this way:
er: "You failed the interview. You didn't consider the risk
of staking them too high and someone being hurt if they
fall over."
ee: "That's not a proper use of the box! The box is
perfectly safe if used properly. On page 206 of the manual
for these boxes it clearly says stack no more than 5 high."
er: "That wouldn't help."
I post this because I don't like analogies, not because it illustrates
my point of view! To come clean, I am probably somewhere in the
middle with a leaning towards the view that errors result from sloppy
programming (in general) as much as from misuse of specific "risky"
functions.
For instance if the boxes look exactly like orgage boxes, which are typically stacked ten high, then the fact that they will topple over if stacked more than five is an obvious danger.
However if established practise in fruit warehouses is to stack boxes no more than three high, and there is nothing about the apple boxes to suggest that they are unusual, then it is not a safety risk. In fact we create a safety risk by sticking a "stack no more than five high" label on it, because it gets people out of the habit of observing notices.
--
Free games and programming goodies.
http://www.personal.leeds.ac.uk/~bgy1mm
.
- References:
- Bug/Gross InEfficiency in HeathField's fgetline program
- From: Antoninus Twink
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard Heathfield
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard Heathfield
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Antoninus Twink
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: santosh
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Antoninus Twink
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: kuyper
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Tor Rustad
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard Heathfield
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Tor Rustad
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Richard Heathfield
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Peter Nilsson
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Peter Pichler
- Re: Bug/Gross InEfficiency in HeathField's fgetline program
- From: Ben Bacarisse
- Bug/Gross InEfficiency in HeathField's fgetline program
- Prev by Date: Re: Bug/Gross InEfficiency in HeathField's fgetline program
- Next by Date: Re: How can i read the stack frames of running process?
- Previous by thread: Re: Bug/Gross InEfficiency in HeathField's fgetline program
- Next by thread: Re: Bug/Gross InEfficiency in HeathField's fgetline program
- Index(es):
Relevant Pages
|
|