[Openmcl-devel] Trunk and released version

Ron Garret ron at flownet.com
Thu Aug 13 07:55:01 PDT 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))
>>        stuff-involving-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
> http://clozure.com/mailman/listinfo/openmcl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20090813/0370c263/attachment.htm>

More information about the Openmcl-devel mailing list