[GBBopen-developer] SBCL and compiled closures

[Wendall Marvel]

Hi,

I'd forgotten I'd set *evaluator-mode* to :interpret in my .sbclrc for
something else I was doing - if I set it back to :compile both
initiate.lisp and startup.lisp load just fine.

I get an SB-EVAL::INTERPRETER-ENVIRONMENT-TOO-COMPLEX-ERROR on attempts
to load either file with *evaluator-mode* set to :interpret, in both the
1.0.17.31 version I was running and 1.0.18.12

(mini-module:compile-module :gbbopen-test :propagate :create-dirs)
doesn't pitch any errors with the patch applied and *evaluator-mode* set
to :interpret (although there are a fair number of warnings, I'm not
sure if they're expected or not).

Thanks,
Wendall



Dan Corkill wrote:
> 
>> I pulled GBBopen from svn today, and SBCL seems to have the same trouble
>> with compiling closures as CMUCL and Lispworks ... I added sbcl to the
>> three appropriate read-time conditionals, and building the gbbopen-user
>> package and instantiating a unit instance (as specified in the tutorial)
>> seems to work OK, although I haven't done more than that (yet).
> 
> What version of SBCL and platform are you using?  SBCL 1.0.18 just
> passed regression testing on Linux (Fedora) and OSX (Intel & PPC) a few
> days ago...
> 
> 



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.