[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: SETF-OPTIONAL-ARGUMENTS (Version 1)
- To: CL-Cleanup@SAIL.Stanford.EDU
- Subject: Issue: SETF-OPTIONAL-ARGUMENTS (Version 1)
- From: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Wed, 1 Feb 89 15:06 EST
- In-reply-to: <890201143749.0.KMP@BOBOLINK.SCRC.Symbolics.COM>
Someone here just pointed me at p165 for GET and p167 for GETF.
Also, it came up that the 2nd to nth return value in my test
case were wrong, making this a non-issue for GETHASH, since
the found-p information reveals whether you've cheated.
Nevertheless, the issue remains for user-defined functions
and we should probably offer general advice with SETF rather
than point by point advice on consumers like GET and GETF,
so that users will know what the general rule is.