Is there any particular effect you think would be useful at load time that wouldn't be better done at compile-time?
The main application - monitoring changes in the Lisp system after loading the code (see attachment)
Main concept code: (let ((old-all-packages (list-all-packages))) (load *test-file*) (set-difference (list-all-packages) old-all-packages))
i am don't know need whether add :around-load key, but need tracking changes in lisp image. Example: tracking new packages.
Moreover, need to check that the component entities will provide such packages: (: file "somefile": provided (: packages (: pkg1: pkg2)))
Втр 18 Окт 2011 18:41:59 +0400, Far fahree@gmail.com написал:
On Tue, Oct 18, 2011 at 10:22, Сергей Катревич linkfly1@newmail.ru wrote:
:around-compile - wonderful solve of problem! Can add the :around-load for similar purpose? This it seems logical.
Thanks for the appreciation!
I think :around-load is a bad idea, for reasons that Juanjo and I mentioned previously in this discussion: it doesn't play well with the link model used by ECL, XCVB, FASL-concatenators, etc. The whole idea of a FASL is that it is fully formed and easy to load in a simple way; if wrapping is required around the load, then something wrong is happening.
Is there any particular effect you think would be useful at load time that wouldn't be better done at compile-time?
On the other hand, I now realize that load-source-op should probably heed the around-compile hook.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org To authorize all commercial relations between consenting adults.