11 Oct
2010
11 Oct
'10
4:08 p.m.
On 11 October 2010 18:10, Faré <fahree@gmail.com> wrote:
Apparently, this was a big fail, and you need to remove FASLs compiled with versions of ASDF earlier than 2.006 if any of them uses internal ASDF utilities. My apologies for the big mess.
I wanted to take this as an opportunity to point to the recent question "can we determine fasl-compatibility without loading the fasl"? No. While you may be able to approximate it with implementation-specific fasl-header tests, there can always be stuff in fasls that breaks compatibility anyways -- as demonstrated above. Cheers, -- Nikodemus