From ... From: Erik Naggum Subject: Re: dealing with errors (was: "Programming is FUN again") Date: 1998/03/30 Message-ID: <3100267758827468@naggum.no>#1/1 X-Deja-AN: 339177333 References: <6e9p0b$h0j@er3.rutgers.edu> <6ec6os$7a@bgtnsc03.worldnet.att.net> <6ecbd5$epg$1@client3.news.psi.net> <6f0m6n$71u$1@news.hal-pc.org> <351692EA.41C6@bogus.acm.org> <351A72C3.5CEF1977@badlands.nodak.edu> <3099927027198005@naggum.no> <351FBDB2.49A6D9B1@badlands.nodak.edu> mail-copies-to: never Organization: Naggum Software; +47 8800 8879; http://www.naggum.no Newsgroups: comp.lang.lisp * Brent A Ellingson | I didn't write that assumptions should should go uncheck, or that all | errors should be ignored, or even that ignoring errors is in general the | best policy. What I remember writing is that this report makes it pretty | clear that ignoring *this* error in *this* situation would have been a | *better* policy than allowing non-critcal code to crash both the main and | backup guidance systems of the rocket, ultimately causing the rocket to | be torn to shreds by the atmosphere. I am unable to understand that you are _not_ saying that the cause of the failure was that there should have been an exception handler (that did nothing) for this situation, but wasn't, and this flies in the face of the gist of the report, which was, and I repeat myself: that the bug was to let code run that should not have run to begin with. ObCL: IGNORE-ERRORS is an exception handler. #:Erik -- religious cult update in light of new scientific discoveries: "when we cannot go to the comet, the comet must come to us."