14 Nov
2009
14 Nov
'09
3:29 p.m.
On Sat, Nov 14, 2009 at 09:37:06AM +0100, Hans Hübner wrote:
We faced this problem a few times in the past and had the luxury to fix the underlying libraries. Normally, removing the use of ignore-errors is not hard to do, and quality code does not use it anyway. Face it, using (ignore-errors (parse-integer ...)) is nothing but stupid, but that was where I had to repair stuff in the past to make it debuggable.
A perfectly sane pattern however is catching a specific error, e.g.
(handler-case (parse-integer ...) (parse-error () nil))
This also triggers a break, of course.
Leslie