[Openmcl-devel] Trunk and released version
ron at flownet.com
Thu Aug 13 10:55:01 EDT 2009
I'd call that a bug in the ANSI spec. It violates the principle of
least surprise for no benefit whatsoever. If X is unconditionally
bound to NIL then there is no point in even having it in scope when
the result-form is evaluated.
On Aug 13, 2009, at 6:28 AM, Tim Bradshaw wrote:
> On 13 Aug 2009, at 12:31, Arthur W Cater wrote:
>> a form like
>> (dolist (X list-of-xs expr-not-using-X)
>> (declare (type mytype X))
>> provoking a complaint that NIL is not of type MYTYPE
> I'm pretty sure that's not a bug. X is defined to be bound to NIL
> when the result-form is evaluated. So unless NIL is an instance of
> MYTYPE your declaration is wrong.
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel