From: Nikodemus S. <tsi...@cc...> - 2003-09-04 12:24:24
Attachments:
fasl.patch
|
Hi, The attached patch provides a new condition: sb-ext:invalid-fasl, subtypes of which may be signalled by LOAD, so that user code can detect wrong fasl-versions, etc handle handle them. Also includes ASDF-machinery to recompile on such errors. Cheers, -- Nikodemus |
From: Andreas F. <as...@bo...> - 2003-10-17 15:48:14
|
On 2003-09-04, Nikodemus Siivola <tsi...@cc...> wrote: > The attached patch provides a new condition: sb-ext:invalid-fasl, > subtypes of which may be signalled by LOAD, so that user code can > detect wrong fasl-versions, etc handle handle them. Also includes > ASDF-machinery to recompile on such errors. I applied a slightly modified version of this to 0.8.4.28. For those who want to experience the ASDF magic, I have: (defmethod asdf:perform :around ((o asdf:load-op) (c asdf:cl-source-file)) (flet ((recompile () (asdf:perform (make-instance 'asdf:compile-op) c))) (handler-case (call-next-method o c) (sb-ext:invalid-fasl () (recompile) (call-next-method o c))))) in my ~/.sbclrc. This recompiles FASLs which fail to load with the INVALID-FASL code. Thanks, -- Andreas Fuchs, <as...@ac...>, as...@ja..., antifuchs |