[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- To: (BUG LISP) at MIT-MC
- From: KMP at MIT-MC (Kent M. Pitman)
- Date: Thu, 18 Jan 79 07:53:00 GMT
- Original-date: 18 JAN 1979 0253-EST
If what's in UNDF-FNCTN calls an undefined function, Lisp will .VAL 0
rather than something more reasonable. I wouldn't object to it either
recursing on itself (on the off chance that it could fix the problem!)
or doing a FAIL-ACT breakpoint in this case, but what it does now makes
it hard to debug a new UNDF-FNCTN handler ... -kmp