Gilles Tran <gitran_nospam_@wanadoo.fr> wrote:
> Because from a user's point of view, it's the same : the computer was
> working fine, and suddenly it doesn't, and this is how it appears to the
> user and this is what matters first to him/her.

  But there's an important difference from the point of view of the user:
If the program crashes it doesn't say the exact reason why it stopped and
thus there's no hint about what to do next. If it is giving an error
message, it is telling the exact reason why it stopped and thus the user
can get an idea of what to do to fix the problem.

  If you try to open the door of a car with the wrong key and the door
doesn't open, did the car crash? Of course not. However, that's exactly
what the users are saying about programs which are only showing normal
behaviour on invalid or incomplete input (or lack of resources).

-- 
#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