Thorsten Froehlich <tho### [at] trfde> wrote:
> That is not a crash but a simple error POV-Ray reports!  A crash is the
> result of a program malfunction.  An error properly reported due to your
> scene consuming all available memory is not a program malfunction.

  I have a co-worker which has the really bad habit of using the word
"crash" (well, the Finnish equivalent) for both program malfunction (eg.
segmentation fault) and a properly ended program issuing a proper error
message.
  A typical conversation of ours goes like he explaining me a new feature
he has added to one part of our project, then I ask what happens if I
give it a certain patological input, he thinks a couple of seconds and
says that the program crashes.
  I have no way of knowing if he meant that I came up with a bug in
his code which causes the program to really crash, or if he meant that
the program correctly detects the invalid input and gives an appropriate
error message and stops. I have to ask him explicitly each time.
  For some reason he never learns the correct terminology, even though
this same thing has happened many times. He intuitively says "crashes"
when talking casually without thinking too much about the true meaning
of the word.

  So it's not an isolated case, but seems to be fairly common. I wonder
why this is so.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message