[asdf-devel] Port of ASDF 126.96.36.199 to MKCL
fahree at gmail.com
Tue Mar 25 19:16:58 UTC 2014
>> 3- if I uncomment the lines:
>> ;;(unless (or #+ecl (use-ecl-byte-compiler-p))
>> ;; (setf *load-system-operation* 'load-bundle-op))
>> I get an error in test-logical-pathname,
>> with the .fasb apparently mapped to the wrong directory.
> ???! What is the real need for this one? You see me a bit baffled here. Will
If I understand correctly the case that Juanjo once made, the real
need is that dlopen of a lot of small fasls seems to be more expensive
than for a few big bundles — and also that if you depend on a lot of
systems and have them loaded via load-bundle-op, then need to
recompile one file, this happens through load-op which will cause all
the previous systems to be re-loaded via load-op.
With (setf *load-system-operation* 'load-bundle-op), all the
already-compiled dependencies are loaded as bundles, and only systems
in need of recompilation are compiled with compile-op, load-op, and
then again compile-bundle-op and load-bundle-op.
Unhappily, there are bugs, and at least on ECL, loading two different
versions of the same library seems to lead to cases where the old one
shadows the new one, or something. egrep '#.*(e|mk)cl' asdf/test/ can
give a few hints, particularly in test-bundle.script and
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
As far as we know, our computer has never had an undetected error.
More information about the asdf-devel