On Fri, Jul 26, 2013 at 1:27 PM, Stelian Ionescu sionescu@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 :
- (asdf:load-system :swap-bytes/test :force t) does not recurse
into :defsystem-depends-on deps. Is this intentional ?
On Fri, Jul 26, 2013 at 2:04 PM, Faré fahree@gmail.com wrote:
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.
So I started working on that by defining a function load-systems* that accepts a list of systems and keywords (unlike load-systems). [Patch attached]
Issue: even once such a function is defined, I realized that ASDF3 does NOT have a special variable *force* or *plan* or anything from which to extract which :force value to use. I'm not convinced that such a special variable would be a win. In any case, adding one is an architectural decision for the maintainer, not a superficial change that a non-maintainer like me can take. [And if I were still maintainer, I would have a strong prejudice against it, and wouldn't see this current feature request as a sufficient motivation to add such a variable.]
Therefore, this patch does the easy part of the job of defining a new function, but doesn't actually propagate require flags through defsystem-depends-on'dencies.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Young man, in mathematics you don't understand things, you just get used to them. — John von Neumann (1903-1957)