[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
issue SHARP-COMMA-CONFUSION
- To: masinter.pa@Xerox.COM
- Subject: issue SHARP-COMMA-CONFUSION
- From: Jon L White <jonl@lucid.com>
- Date: Fri, 13 Jan 89 19:18:39 PST
- Cc: sandra%defun@cs.utah.edu, cl-compiler@sail.stanford.edu, KMP@STONY-BROOK.SCRC.Symbolics.COM
- In-reply-to: masinter.pa@Xerox.COM's message of 11 Jan 89 23:43 PST <890111-234404-11837@Xerox>
re: It treats #, more like , than like #. and gives a consistent
interpretation of it.
Right. So now it is
(1) useless for those who thought they know how to use the former,
inherently broken definition of #, and
(2) redundant with the new special form LOAD-TIME-EVAL.
I agree with Kent and Sandra that fixing up #, like this -- which will
inevitably lead to these two undesirable results -- is the worst of all
the possible things we could do.
Having looked ahead in the mails - - I see there will be some
"quibbling" as to how to acknowledge that vendors will continue to
supply some of the deleted or deprecated features of Common Lisp 1984.
I think this will be a very serious issue sooon, so maybe we should
start a discussion under a new Subject heading?
-- JonL --