[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Proposal #7: TYPE-SPECIFIER-P
- To: common-lisp@SU-AI.ARPA
- Subject: Proposal #7: TYPE-SPECIFIER-P
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Mon, 28 Jul 86 20:24 EDT
- In-reply-to: <FAHLMAN.12224580594.BABYL@C.CS.CMU.EDU>, <860721-221520-2564@Xerox>, <860722-102542-2911@Xerox>, <860722174822.6.DCP@FIREBIRD.SCRC.Symbolics.COM>, <[G.BBN.COM]23-Jul-86 02:30:50.NGALL>, <860723130828.1.DCP@FIREBIRD.SCRC.Symbolics.COM>, <8607272237.AA21099@lmi-angel.ARPA>, <FAHLMAN.12226129722.BABYL@C.CS.CMU.EDU>, <FAHLMAN.12226153071.BABYL@C.CS.CMU.EDU>, <860728111011.1.DCP@FIREBIRD.SCRC.Symbolics.COM>, <860728-123623-2787@Xerox>
TYPE-SPECIFIER-P is an appropriate name for a function that takes an
(OR SYMBOL LIST) and tells whether it's a valid specifier. If you're
going to replace this with a function that takes a SYMBOL and tells
whether it's the name of a type, call it TYPE-NAME-P.
However, I agree with Masinter's comment that we should concentrate on
fixing what is wrong with the language rather than adding more features.
I have no objection to either of TYPE-SPECIFIER-P or TYPE-NAME-P if
someone can show why these are needed to fix something wrong with the
language. Perhaps Guy can comment on why the original proposal 51 in
his clarifications list was tagged with an asterisk indicating that it
corrects an important flaw or resolves an ambiguity in the
specification.