[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documentation strings and function.
- To: Bobrow.pa@Xerox.COM, DCP@QUABBIN.SCRC.Symbolics.COM
 
- Subject: Re: Documentation strings and function.
 
- From: David C. Plummer <DCP@QUABBIN.SCRC.Symbolics.COM>
 
- Date: Thu, 4 Sep 86 18:13 EDT
 
- Cc: Rice@SUMEX-AIM.ARPA, Fahlman@C.CS.CMU.EDU,    KMP@STONY-BROOK.SCRC.Symbolics.COM, Common-Lisp@SU-AI.ARPA
 
- In-reply-to: <860904-140042-1593@Xerox>
 
    Date: 4 Sep 86 13:58 PDT
    From: Bobrow.pa@Xerox.COM
      If multiple doc strings are allowed, what does parse-body
     (if we ever decide on what that should be and do) return? 
    A single string or a list of such, so that these are distinguished.
I would prefer that the result would always (SATISFY LISTP).  This would
let macros do
	,@doc-strings
instead of
	,@(if (stringp doc-strings) `(,doc-strings) doc-strings)
as well as what DOCUMENTATION returns.  I think this is the case where
optimizing a singleton list to be its single component does more harm
than good.