On 08/23/08 07:36, Kent West wrote:
Ron Johnson wrote:On 08/23/08 02:18, Rich Healey wrote:Ron Johnson wrote:On 08/22/08 23:04, Daniel Watkins wrote:If you get a segmentation fault, that suggests that the code being compiled is faulty.Blame the compiler???? That's a CompSci 101 mistake.Erm.. I believe he was blaming the coder :PThen why didn't he just say that? "Segfault means you wrote buggy code."I thought that's what he said, just in different words: "the code being compiled is faulty" = "you wrote buggy code".
Passive voice vs. active voice."[T]he code being compiled is faulty" implies that the "the code" did something to make itself broken, whereas "you wrote buggy code" places the blame squarely on target: the human.
(This could be construed as an example of the femininization of man, but I won't go there...)
-- Ron Johnson, Jr. Jefferson LA USA "Do not bite at the bait of pleasure till you know there is no hook beneath it." -- Thomas Jefferson