On Fri, Apr 16, 2010 at 12:01 AM, james anderson <span dir="ltr"><<a href="mailto:james.anderson@setf.de">james.anderson@setf.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;">you will need to elaborate on why this matters. the primary dependencies are all in a list which is bound to the in-order-to slot.<div>the :in-order-to initarg is just circumstantially involved in this. most of the initialization value is collected from the other dependency initargs.</div>
</div></blockquote><div><br>Yes, but everything is transformed into an in-order to internally when parsing the system definition. The result is a duplicated list of dependencies :in-order-to load-op and :in-order-to compile-op. <br>
<br>The additional problem is that right now we have a dichotomy between load and load-src-op and apart from the cases in which :in-order-to is used for testing, the other cases just write dependencies for one of the operations and not for the other.<br>
<br>The third problem is that the in-order to mechanism does not provide any kind of inheritance and if I tried to write a fix for load-src-op that creates the hierarchy<br><br>operation<br>+- compile-op<br>+- load-op<br>
+- compile-and-load-op<br> +- load-source-op<br><br>this does not work.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><div>your remarks suggest that you fail to appreciate how broken i believe traverse to be.[1]</div></div></div></blockquote><div><br>Your remarks fail to appreciate how good and useful I believe a properly written traverse could be.<br>
</div></div><br>Juanjo<br clear="all"><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>