[slime-devel] Re: make swank safe if loaded into an image with an older version of swank in the image

[Marco Baringer]

Madhu <enometh at meer.net> writes:

> This is a bad idea. In general, packages should not be automatically
> deleted[1], and I would prefer if package deletion was provided in a
> function called reload-swank-loader or something that the user can
> call when he knows what is happening
>
> Secondly, this breaks a common[2] strategy to put swank fasl files in a
> different location: For example in my lisp's init file I may have have
>
> (eval-when (:load-toplevel :execute :compile-toplevel)
> (unless (find-package :swank-loader)
>   (make-package :swank-loader)))
>
> (defparameter swank-loader::*fasl-directory* "/user11/madhu/build/swank/")
>
> (load "/path/toswank-loader.lisp")
>
> - To override the defvar in swank-loader.lisp

ok, since we even suggest doing this is the documentation i will stop
deleting the swank-loader package (but i'll keep deleting the other
packages unless you can convince me otherwise).

> The logic propsed in the patch would break this usage completely by
> deleting the package the variable belongs to
> --
> Madhu
>
> [1] I hear some implementations may leak objects in deleted packages

which implementations? they should be fixed.

-- 
-Marco
Ring the bells that still can ring.
Forget your perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen