Re: [slime-devel] [patch] Make it possible to keep FASL files in source directory
This makes swank no longer asdf loadable. E.g. http://paste.lisp.org/display/15792 The problem is that UCW depends upon swank, but just stating that dependency in the asd is no longer good enough. All the swank packages aren't there until the load-swank function is called, and since files in UCW reference the swank package we get a reader error. The name "SWANK-BACKEND" does not designate any package. Can we please make swank continue to be fully loaded by default? Maybe make several ASD files, one similar to the current swank.asd that just makes swank-loader available, and another that also loads a file that does (swank-loader:load-swank) ? Any thoughts? Nathan Bird
* Nathan Bird [2006-01-19 00:23+0100] writes:
Can we please make swank continue to be fully loaded by default? Maybe make several ASD files, one similar to the current swank.asd that just makes swank-loader available, and another that also loads a file that does (swank-loader:load-swank) ?
I reverted that change and swank-loader now loads the rest as before.
Any thoughts?
We wanted some way to customize the fasl directory, so I had separated the loading of the loader and the loading of the rest. The drawback of that approach was that swank-loader:load-swank had to be called explicitly to pass in the customized parameters and that's inconvenient for those who don't need the customization (i.e. most people). So, I reverted that part. The new way to customize the fasl directory is to set the variable swank-loader:*fasl-directory* before loading swank-loader. The drawback of this variant is that the swank-loader package must exist (or must be created) before the variable can be set. I think this is the better tradeoff because most users don't need the customization and only the others have to pay the price for more flexibility. Helmut.
participants (2)
-
Helmut Eller -
Nathan Bird