[Openmcl-devel] bad defclass causing side effect

Hamilton Link hamlink at comcast.net
Sun Jun 13 21:25:29 UTC 2004


To me this isn't doesn't look so much like odd persistent behavior as 
undesirable side effects when you redefine a class badly (still, looks 
like a bug).

The first bad defclas doesn't create a class, but once BAR is created 
(with your second call) the error from the subsequent redefinition 
should probably (but doesn't) prevent a side effect on the class. Then 
when you try to redefine the class again in a valid way, it looks at 
the now-broken class and chokes... seems like a bug just from a DWIM 
standpoint but I don't know what the letter of the law is on when 
defclass side effects take place, that would be a question for Gary.

h

On Jun 10, 2004, at 11:57 AM, Gary King wrote:

> OpenMCL (0.14.2) has an odd persistent behavior with respect to class 
> definitions. If you evaluate the following four forms, you'll see what 
> I mean. The fourth form should work but somehow the error remains.
>
> ;;; gets an error
> (defclass bar ()
>   ((documentation :reader documentation)))
>
> ;;; works
> (defclass bar ()
>   ())
>
> ;;; gets an error
> (defclass bar ()
>   ((documentation :reader documentation)))
>
> ;;; also gets an error !!
> (defclass bar ()
>   ())
>
> -- 
> Gary Warren King, Lab Manager
> EKSL East, University of Massachusetts * 413 577 0176
>
> “Trusting to escape scrutiny by fixing the public gaze upon the 
> exceeding brightness of military glory, that attractive rainbow that 
> rises in showers of blood —that serpent’s eye, that charms to destroy, 
> he plunged into war.”
>   -- Abraham Lincoln (of James Polk, his president and the 
> commander-in-chief)
>
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>





More information about the Openmcl-devel mailing list