This brings back one of the things I discussed long ago. TRAVERSE&#39;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.<br>
<br>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)) <br><br><div class="gmail_quote">
On Wed, Mar 17, 2010 at 9:58 AM, Juan Jose Garcia-Ripoll <span dir="ltr">&lt;<a href="mailto:juanjose.garciaripoll@googlemail.com">juanjose.garciaripoll@googlemail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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.<br><br>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.<br>

<br>Why such an incompatible change? It definitely screwed up ALL of ECL&#39;s extensions.<br><br>Juanjo<br clear="all"><font color="#888888"><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br>
<a href="http://tream.dreamhosters.com" target="_blank">http://tream.dreamhosters.com</a><br>

</font></blockquote></div><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://tream.dreamhosters.com">http://tream.dreamhosters.com</a><br>