[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FERROR/CERROR & LOOP
- To: JLK at MIT-MC
- Subject: FERROR/CERROR & LOOP
- From: Robert W. Kerns <RWK at MIT-MC>
- Date: Wed, 30 Apr 80 22:11:00 GMT
- Cc: BUG-LISP at MIT-MC, GSB at MIT-MC, REES at MIT-MC
- Original-date: 30 April 1980 18:11-EDT
- Sender: ___037 at MIT-MC
I do not think LOOP should be made autoloadable, at least at this time. At
least not until I read the documentation (c'mon GSB, proselytize me!) ...
Seriously, what implementation of FERROR/CERROR do you propose MacLisp
autoload? There are several possible, from my SIGNAL package which converts
various MacLisp errors into signals and throws you into a debugger, etc., to
macros which turn into ERROR. If you refer to the version which is in EXTEND,
that is a stopgap FERROR intended to be replaced by whatever more winning
version the user has. It's there in case the user DOESN'T have ANY version.
It loses. (Hmm, it should live in a separate file and be made to autoload,
so that it can't clobber any definition the user has loaded BEFORE extend!)