[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue CLOS-CONDITIONS, v4
- To: kmp@SCRC-STONY-BROOK.ARPA
- Subject: Issue CLOS-CONDITIONS, v4
- From: Kim A. Barrett <IIM%ECLA@ECLC.USC.EDU>
- Date: Sat 11 Mar 89 19:32:37-PST
- Cc: cl-cleanup@SAIL.STANFORD.EDU, iim%ECLA@ECLC.USC.EDU
I would like to second Richard Mlynarik's suggestion of a REPORT-CONDITION
method, for much the same reasons he mentioned. It's really ugly to have to
always include the check for *PRINT-ESCAPE* with a CALL-NEXT-METHOD every time
you want to define your own report method for a condition.
kab
-------