[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: WGD at MIT-MC
- From: Glenn S. Burke <GSB at MIT-ML>
- Date: Mon, 28 Sep 81 05:59:00 GMT
- Cc: BUG-MACLISP at MIT-MC
- Original-date: 28 September 1981 01:59-EDT
Date: 27 September 1981 16:33-EDT
From: William G. Dubuque <WGD at MIT-MC>
Sender: BIL at MIT-MC
How come a recursive wrng-no-args break calls the system supplied handler
even when a user handler exists as the value of wrng-no-args?
Errors which are going to immediately bomb out to errsets don't even
call the handler; they just do (essentially) (ERRPRINT NIL), which is
what all the default handlers do anyway. This is presumably what is
happening to you? If in fact you make them stack by doing something
like (setq errset 'car) then the correct handler gets called.