On Jan 21, 2013, at 20:08, Faré wrote:
> ABCL is one of the three implementations, together with CLISP and CMUCL,
> where I ultimately punted on ASDF hot-upgrade, by just trying to
> rename away the ASDF package if it's too old.
>
> I don't know if you're interested in making the kind of packag
CMUCL is one of the three implementations, together with ABCL and CLISP,
where I ultimately punted on ASDF hot-upgrade, by just trying to
rename away the ASDF package if it's too old.
My package surgery looks like it works, but it looks like CMUCL refuses
to invalidate old CLOS methods when I fmak
On Mon, Jan 21, 2013 at 11:51 AM, Sam Steingold wrote:
>> * Faré [2013-01-20 22:46:35 -0500]:
>>
>> Of all the lisp implementations, CLISP has given me the most trouble
>> with ASDF upgrade. Unlike all other Lisps, it won't let me undefine
>> functions and redefine them in the same fasl file. S
ABCL is one of the three implementations, together with CLISP and CMUCL,
where I ultimately punted on ASDF hot-upgrade, by just trying to
rename away the ASDF package if it's too old.
I don't know if you're interested in making the kind of package
surgery I was indulging in work,
but it involves r
> * Faré [2013-01-20 22:46:35 -0500]:
>
> Of all the lisp implementations, CLISP has given me the most trouble
> with ASDF upgrade. Unlike all other Lisps, it won't let me undefine
> functions and redefine them in the same fasl file. Somehow, I always
> end up with CLISP either complaining that
