From: Peter K. <ps...@cs...> - 2012-05-16 03:35:54
|
On Wed, May 16, 2012 at 07:02:49AM +0400, Stas Boukarev wrote: > Patrick Stein <pa...@nk...> writes: > > > So, there's no accounting for the fact that this division might have side-effects? > > > > … Patrick > It doesn't have side-effects, except for the error, which i don't think > anyone would desire. If you want to check everything, run with (safety > 3), which is the definition of safe code by CLHS. If one were writing a video game where one didn't want to check for a division by zero to speed up the computation (just handling the condition in a handler-bind when it happens) that would be a plenty good reason to want the divide-by-zero condition. I've often been surprised by the times that SBCL's default safety settings don't cause certain conditions, like unbound-variable conditions and such, to be signaled at the appropriate times. I know now to set saftey to 3 to get safe code, but it was a surprising road to find that out. I figured I would just get safe code by default. Thank you. -pete |