[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: initial probs with MCL 2.0b1p2
- To: spector@cs.UMD.EDU (Lee Spector)
- Subject: Re: initial probs with MCL 2.0b1p2
- From: Gary Byers <gb>
- Date: Tue, 14 May 91 19:56:38 EDT
- Cc: email@example.com
- In-reply-to: <9105142244.AA12134@mimsy.UMD.EDU>; from "Lee Spector" at May 14, 91 6:44 pm
> I just got MCL 2.0b1 and I'm having a couple of problems; I'd appreciate
> any advice people can offer. I've applied the patches, so I'm running
> MCL 2.0b1p2. I also did (reindex-interfaces) after applying the types
> Disclaimer: I haven't read the entire manual (or all of the source
> code!) yet, but I have looked for info on these issues. Please pardon
> any glaring naivete. Since a lot of people are probably upgrading
> about now, I figured I wouldn't be reticent with my questions.
> - I can't seem to get restart-case or restart-bind to work. The condition
> system is new to me, but CLtL2 p. 877 says:
> "As a trivial example, one could write:
> (restart-case (invoke-restart 'foo 3)
> (foo (x) (+ x 1)))
> to add 3 to 1, returning 4."
> When I try this I get:
> ? (restart-case (invoke-restart 'foo 3)
> (foo (x) (+ x 1)))
> ;Compiler warnings :
> ; Undeclared free variable CCL::$V_ISTRUCT, in an anonymous lambda form.
> > Error: Unbound variable: CCL::$V_ISTRUCT
> > While executing: #<Anonymous Function #x42E03E>
> > Type Command-/ to continue, Command-. to abort.
> > If continued: Retry getting the value of CCL::$V_ISTRUCT.
> See the RestartsI menu item for further choices.
> 1 >
> Something similar happens when I try to use restart-bind. Have I failed
> to require some library module? Is the condition system just not complete?
> (I mean, beyond the error classification incompleteness mentioned in
> the release notes.)
> Thanks! -Lee (firstname.lastname@example.org)
(defconstant ccl::$v_istruct 44)
This constant (which is defined in "library;lispequ") needn't be getting
referenced. Until a fairly late alpha release, we'd been including that
file in the distributed image so hadn't noticed that some macros were
expanding into code which references things defined there.