[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue SHARP-COMMA-CONFUSION
- To: firstname.lastname@example.org
- Subject: Re: issue SHARP-COMMA-CONFUSION
- From: masinter.pa@Xerox.COM
- Date: 5 Jan 89 21:33 PST
- Cc: masinter.pa@Xerox.COM
- In-reply-to: email@example.com (Sandra J Loosemore)'s message of Tue, 3 Jan 89 15:30:43 MST
Actually, I think this is bogus. The simple portable way to handle #, is to
have the compiler use a a readtable which has ' defined as a readmacro like
` but which looks for #, instead of , and then wraps LOAD-TIME-EVAL around
the #,'d forms.
`(a b ,c) reads as (internal:backquote (a b (internal:comma c)))
'(a b #,c) reads as (internal:load-time-quote (a b (internal:load-time-eval
only in the compiler's read macro.
Normally, #, has the same read behavior as #. so program-analyzing programs
wont even see it.
I wouldn't mind getting rid of #., #, and #+ and #-, since they *all* have
the problem that program analyzing programs don't see them. However, I see
little point of removing one without getting rid of the rest of 'em, too.