[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue SHARP-COMMA-CONFUSION
- To: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Subject: Re: issue SHARP-COMMA-CONFUSION
- From: sandra%defun@cs.utah.edu (Sandra J Loosemore)
- Date: Fri, 6 Jan 89 18:05:59 MST
- Cc: Masinter.PA@Xerox.COM, CL-Compiler@SAIL.Stanford.EDU
- In-reply-to: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>, Fri, 6 Jan 89 19:05 EST
I agree with Kent on this one. The time when #., #+, and #- are
processed is *always* read-time, and they always behave the same way
regardless of whether the thing that is doing the reading is the
compiler, LOAD, or some user-written program-analyzing program.
Incidentally, the writeup for this issue does point out that program
analyzers can (theoretically, at least) handle #, by fiddling with the
readtable.
In any case, since the other read macros have nothing to do with
compilation, a proposal to change them wouldn't really fall into our
domain.
-Sandra
-------