[asdf-devel] Problems with asdf:load-system :force

[Faré]

Yes, this is probably a bug. In register-system-definition, we should
get the force argument, and propagate to a variant of load-systems
that itself should take keyword arguments, and is called by
load-systems.

Regarding swap-bytes, there may (or may not) be useful stuff in
sb-rotate-bytes and nibbles.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Director is a misnomer. You're a hoper. You put all these people together and
you hope it all works out.  — Frank Oz, director of "Dirty Rotten Scoundrels"


On Fri, Jul 26, 2013 at 1:27 PM, Stelian Ionescu <sionescu at cddr.org> wrote:
> While working on the test suite of swap-bytes on SBCL(you'll need
>>=1.1.6 I think), I noticed two unexpected results in using :force :
>
> 1) (asdf:load-system :swap-bytes/test :force t) does not recurse
> into :defsystem-depends-on deps. Is this intentional ?
>
> 2) (asdf:load-system :swap-bytes/test :force '(:swap-bytes/test))
> needlessly compiles files from :swap-bytes on which it depends.
> I've attached a log that traces PERFORM and COMPUTE-ACTION-STAMP and
> shows that two files from :swap-bytes get recompiled even though they
> haven't changed.
>
> I'm wondering if the problem lay with the ASDF extension in
> Madeira-port, but that's so simple I can't find any obvious fault.
> Ideas ?
>
> If you want to test for yourselves clone
> https://github.com/sionescu/madeira-port.git and
> https://github.com/sionescu/swap-bytes.git
>
> --
> Stelian Ionescu a.k.a. fe[nl]ix
> Quidquid latine dictum sit, altum videtur.
> http://common-lisp.net/project/iolib
>