On Wed, Mar 07, 2001 at 02:19:00PM +0100, Martin Atzmueller wrote:
> I ran into a problem using the bleeding edge CVS version of sbcl.
> Well, bare sbcl-0.6.11 works, so this bug must have been introduced
> If I compile and load mk-defsystem (attached), I get
> debugger invoked on condition of type TYPE-ERROR:
> TYPE-ERROR in SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
> 0 is not of type (OR FUNCTION SB-KERNEL:FDEFN).
I can replicate this problem with 0.6.11.12, but I haven't tried to
figure it out yet.
I've wandered into a mess with what should become 0.6.11.13, where I've
tried to enable a lot more of the new INTERSECTION-TYPE stuff, and I'm
having trouble getting it to boot; and I've done too much work on it
to want to back out and start over. I'm not sure how long it will
take to get that into a stable state (or for me to give up and
start over at 0.6.11.12). After I do, I'll try to find out what's
wrong with the byte interpreter.
> Since you said on the mailing list, that you would continue to work on
> that, this bug may have been fixed by now.
> Otherwise, I hope you can make some sense out of this.
Unless the byte interpreter problem is a weird side effect of some
type system bug, I doubt that the changes in 0.6.11.13 will fix it.
But I can try to fix it after that.
In the meantime, a possible workaround is
(compile-file "defsystem-sbcl-1.lisp" :byte-compile nil)
When I tried that, I got a more familiar error:
error in function SB-C::%DEFCONSTANT:
The constant *FIND-IRIX-VERSION-SCRIPT* is being redefined.
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C