On Wed, Sep 22, 2010 at 8:37 PM, Pascal J. Bourguignon <span dir="ltr">&lt;<a href="mailto:pjb@informatimago.com">pjb@informatimago.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;">

&gt; No. Why? I mean, the separate components are bundled into a single<br><div class="im">
&gt; asdf.lisp and this process is automated (make -f GNUmakefile<br>
&gt; asdf.lisp). There is no new testing burden. I am just advocating for<br>
&gt; some common sense in the ASDF codebase, organizing it in a readable<br>
&gt; and separated way.<br>
<br>
</div>This is an alternative, indeed.<br>
<br>
asdf.lisp: $(ASDF_SOURCES)<br>
        clar asdf.lisp $(ASDF_SOURCES)<br clear="all"></blockquote></div><br>Indeed, eventually one should move my GNUmakefile line from using sed to using some Lisp implementation for repackaging asdf.lisp, ensuring a version number, etc.<br>

<br>Incidentally, I am still amazed at how people here find a 4k source file manageable at all. No organization, functions spread throught the file, no clear navigation structure... If I have a directory with 10 small files, each one devoted to a separate and clear task, I know where I have to go to edit things for that particular topic.<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">http://juanjose.garciaripoll.googlepages.com</a><br>