On Wed, Jun 13, 2012 at 9:22 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@googlemail.com> wrote:
> On Wed, Jun 13, 2012 at 3:38 AM, CRLF0710 <crlf0...@gmail.com> wrote:
>
>> But for the second question i've still got no idea how to deal with
>> that... It seems that cl-utilities library did a hack to asdf, and used
>> another .asd file as a "SOURCE". This doesn't work on ecl... Any idea how
>> to fix it? (I've temporarily removed that part and it worked fine).
>
>
> This cannot be fixed. This is an abuse of ASDF and ECL has no way to learn
> which ASDF files it has to compile in -- which it should not, for ASDF
> should just be plain declarations of intentions, not code (see
> http://tream.dreamhosters.com/tream/musings/49-lisp/76-analysis-of-existing-asdf-files
> )
Well, actually my sentence is a bit too dramatic: it can be fixed... by
changing the library and telling its maintainer to commit the change, which
should probably be trivial: split out the code that is in ASDF into a
separate file and list it as a dependency!
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
