[slime-devel] Why not adopt asdf?
gendl at genworks.com
Sat Jan 19 23:10:19 UTC 2013
Yay for that plan.
When Allegro came out with 9.0 SMP (with incompatible fasls to the non-SMP)
the swank fasls from SMP were colliding with the ones left over from a
previous non-SMP startup... I submitted a patch for it and it's fixed now.
Not a really big deal (at least for me, but did create work for Helmut
too), but even that kind of little dance will not be needed if swank can
just go ahead and start using asdf:*output-translations* for its fasls.
On Sat, Jan 19, 2013 at 5:32 PM, Faré <fahree at gmail.com> wrote:
> Could SLIME adopt ASDF as a way to compile itself and other software?
> I understand that ASDF was quite insufficient for the needs of SLIME
> back in the bad old days, but these days, ASDF 2
> (1) is available via (require "asdf") on *every* implementation
> that has been released in the last two years
> (i.e. not on corman gcl genera rmcl scl - though it runs on all of them)
> (2) already manages a decent FASL cache so SLIME doesn't have to.
> (3) can upgrade itself correctly if needed.
> ASDF has also improved a lot in the last few years.
> The upcoming release 2.27 formalizes a lot of the portability support
> that had accumulated through the years, improves on it,
> and adds features like condition control, saving of deferred warnings,
> image dump and restore, etc.
> In any case, that would be as much bad code duplication that could die.
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> If debugging is the process of removing bugs,
> then programming must be the process of putting them in.
> — Dijkstra
> slime-devel site list
> slime-devel at common-lisp.net
Dave Cooper, Genworks Support
david.cooper at genworks.com, dave.genworks.com(skype)
USA: 248-327-3253(o), 1-248-330-2979(mobile)
UK: 0191 645 1699
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the slime-devel