[GBBopen-developer] SWANK cannot load when using initiate.lisp
Chun Tian (binghe)
binghe.lisp at gmail.com
Thu Apr 17 05:30:33 EDT 2008
Hi,
>
>> If I load initiate.lisp on CCL startup, I cannot load SWANK since
>> the SWANK package already exist.
>
> SLIME (Swank) has changed in a way that has broken GBBopen's
> extended REPL mechanism. We've committed a quick fix for this
> (barely tested) that should provide you with REPL commands in list
> format and keyword REPL commands (with no arguments). We'll improve
> this soon, but the current commit should get you going.
Yes, I just notice this issue...
After your recent commit, there's a error when load initiate.lisp
because of following changes:
+(defvar swank-backend:*after-init-hook* nil
+ "Hook run after user init files are loaded.")
and
-(defpackage :swank
- (:use :common-lisp))
+(unless (find-package ':swank-backend)
+ (defpackage :swank-backend
+ (:use :common-lisp)
+ (:export #:*after-init-hook*)))
It seems that *AFTER-INIT-HOOK* does't exist in SWANK-BACKEND package
(at least yesterday's SLIME trunk). If I load SWANK before
initiate.lisp at startup, the symbol *AFTER-INIT-HOOK* won't be
exported, and I got this:
> Error: Reader error: No external symbol named "*AFTER-INIT-HOOK*"
in package #<Package "SWANK-BACKEND"> .
> While executing: CCL::%PARSE-TOKEN, in process listener(1).
> Type :GO to continue, :POP to abort, :R for a list of available
restarts.
> If continued: Skip loading init file.
> Type :? for other options.
Regards,
Chun Tian (binghe)
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the GBBopen-developer
mailing list