[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: RWK at MIT-MC
- From: Jon L White <JONL at MIT-MC>
- Date: Sat, 25 Jul 81 13:15:00 GMT
- Cc: BUG-LISP at MIT-MC
- Original-date: 25 July 1981 09:15-EDT
Date: Tuesday, 14 July 1981, 15:25-EDT
From: Robert W. Kerns <RWK at MIT-MC>
In-reply-to: The message of 5 Jul 81 01:12-EDT from Jon L White <JONL at MIT-MC>
Date: 5 July 1981 01:12-EDT
From: Jon L White <JONL at MIT-MC>
(SEND <foo>-CLASS 'PRINT) results in ILOPR.
so does the sending of a variety of other msgs, including :PRINT-SELF.
Admittedly, the :PRINT-SELF msg might require all those silly extra
args that PRINT-OBJECT takes, but why can't the PRINT methods default
them to appropriate values?
At least, it shouldn't ILOPR, but die more gracefully.
Why not fix LISP's LSUBR calling sequence, which is at fault here?
Note that the PRINT method is an OBSOLETE name for :PRINT-SELF.
Why not just call the function PRINT, which does the defaulting for you?
I'm not sure what you're suggesting here -- since a PRINT msg is acceptable,
then why should it be totally equivalent to the :PRINT-SELF msg?
The latter can take all the extra args it wants, but the former could
simulate a call to PRINT.