[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: BSG%scrc-stony-brook.arpa@CSNET-RELAY.ARPA
- Subject: Re: keywords
- From: Alan Snyder <AS@HP-HULK>
- Date: Wed 4 Dec 85 08:42:23-PST
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: Message from ""Bernard S. Greenberg" <BSG%scrc-stony-brook.arpa@CSNET-RELAY>" of Wed 4 Dec 85 07:56:31-PST
Symbolics Common Lisp relies heavily on the property lists of keywords.
Given that a keyword is "an indicator that means X in context Y",
it is right reasonable that context Y might want to hang properties off
of it to implement that.
An alternative is to use the keyword as the indicator on a property
list attached to Y, which avoids the potential conflicts in using
a global database (a propertly list attached to a keyword).
It is inevitable that keywords will be interpreted differently
in different contexts. What you want to avoid is conflicts
that would prevent the different contexts from coexisting.
Can a keyword be used as the name of a type?
Can a keyword be used as the name of a block?
Can a keyword be used as a tag?