[asdf-devel] ASDF traverse changed behavior?

[Juan Jose Garcia-Ripoll]

This brings back one of the things I discussed long ago. TRAVERSE's behavior
has to be documented and its behavior has to be specified and fixed. Either
that or ASDF should stabilize a way to write extensions on top of it. I can
not be hanging out there waiting for every improvement in ASDF to break our
build system.

Incidentally, another thing that breaks ECL is that INPUT-FILES now has a
default method with signature ((o operation) ...) That broke our default
methods with signature ((o T) (c compiled-file))

On Wed, Mar 17, 2010 at 9:58 AM, Juan Jose Garcia-Ripoll <
juanjose.garciaripoll at googlemail.com> wrote:

> Before, if an operation defined by me, such as LIB-OP, did not traverse a
> system, then the only operation we got was that operation applied on the
> system, as a generic object.
>
> Now TRAVERSE not only imposes the LIB-OP operation on the system, but it
> also scans the components and imposes the operation on the components.
>
> Why such an incompatible change? It definitely screwed up ALL of ECL's
> extensions.
>
> Juanjo
>
> --
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain)
> http://tream.dreamhosters.com
>

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://tream.dreamhosters.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/asdf-devel/attachments/20100317/cbbb51bd/attachment.html>