On Sat, Feb 5, 2011 at 7:27 PM, Juan Jose Garcia-Ripoll <span dir="ltr">&lt;<a href="mailto:juanjose.garciaripoll@googlemail.com">juanjose.garciaripoll@googlemail.com</a>&gt;</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 class="im">On Sat, Feb 5, 2011 at 7:17 PM, Faré <span dir="ltr">&lt;<a href="mailto:fahree@gmail.com" target="_blank">fahree@gmail.com</a>&gt;</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>Please show me your code if you want me to reconsider.<br></div></blockquote></div><br></div>Please understand that all this is about not *hardcoding* in ASDF what the compiler should or should not do. All you are suggesting is about reader conditionalization (that means one ASDF file per compiler), hardcoding behavior based on externally defined flags (which may or may not exist at all in older or later releases), and other things that overcomplicate the problem.<br clear="all">

</blockquote></div><br>Argghh this does not work at all. I did not realize that ASDF&#39;s compilation now uses a temporary file name. That is really unfortunate because it means we can not really wrap inside compile-file* and also not around compile-file*, and we have to go back to the level of PERFORM.<br>

<br>Attached is a diff where this customization is thus introduced at the only place where it makes sense, and it is done using a single special variable that can be dynamically changed. Seems to work with quicklisp<br><br>

Juanjo<br><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://juanjose.garciaripoll.googlepages.com" target="_blank">http://juanjose.garciaripoll.googlepages.com</a><br>