On 1/28/07, Mario Rodriguez <biomates at telefonica.net> wrote:
> > What happened is that f(x, y) was evaluated for x=0 and y=0,
> > which caused a divison by 0, which was not handled gracefully
> > by plot3d. Sorry for the bother; this is a bug in the plotting code.
> > (Specifically a function named COERCE-FLOAT-FUN.)
>
> This is also a bug to be fixed in 'gpdraw' (ok, ok, let's call it 'draw'
> in the near future :), since it also calls 'coerce-float-fun'.
Well, I wonder where we should try to catch errors -- whether
in the function constructed by COERCE-FLOAT-FUN or in its caller.
Although an error could theoretically be interesting to the caller,
I don't think that's exploited in current Maxima code.
So I guess at this point I'm inclined to say the function constructed
by COERCE-FLOAT-FUN should catch any Lisp or Maxima errors
(and return NIL in those cases).
FWIW
Robert