From: Nathan F. <fr...@ro...> - 2001-03-24 05:44:20
|
DEFSYSTEM was the one thing holding me back from using SBCL exclusively. But then I found the patch from Daniel Barlow which applied without incident on DEFSYSTEM 3.2i from sourceforge. So far, so good. I COMPILE-FILE and whatnot; goes well, complains a little bit more than CMUCL and takes nearly three times as long, but that's no big deal (the x86f file is smaller, any particular reason?). So we do the following: * (load "defsystem") 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). Within the debugger, you can type HELP for help. At any command prompt (within the debugger or not) you can type (SB-EXT:QUIT) to terminate the SBCL executable. The condition which caused the debugger to be entered is bound to SB-DEBUG:*DEBUG-CONDITION*. restarts: 0: [ABORT ] Reduce debugger level (leaving debugger). 1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop. (SB-C::DO-CALL #<code object "top-level form" {900C39F}> 5 6 4 1 T) source: ; file: /home/nathan/lisp/sbcl/src/code/byte-interp.lisp (LET* ((OLD-SP #) (FUN-OR-FDEFN #) (FUNCTION #)) (DECLARE (TYPE STACK-POINTER OLD-SP) (TYPE # FUN-OR-FDEFN) (TYPE FUNCTION FUNCTION)) (TYPECASE FUNCTION (BYTE-FUNCTION #) (BYTE-CLOSURE #) (T #))) 0] Shucks! This is with 0.6.11.13. Any suggestions on what's going wrong here? I'm going to try and grab the new cvs and see if that fixes anything. I don't think it will, but you never know... -- </nathan> fr...@ro... | http://www.rose-hulman.edu/~froydnj/ Yes, God had a deadline. So He wrote it all in Lisp. |