On Thu, Jun 23, 2011 at 3:58 PM, Marko Kocić <[email protected]> wrote:
> Why requiring asdf and then cmp fails, while requiring cmp and asdf works?
>
This only happens in windows, where the bytecmp module (bytecodes compiler)
is loaded by default. The problem is the following one.
Path 1: bytecmp -> cmp -> asdf
This works, as CMP redefines COMPILE-FILE-PATHNAME and ASDF may work with
the new compiler (which replaces the bytecodes compiler without problems).
Path 2: bytecmp -> asdf -> cmp
This does not work. ASDF overwrites REQUIRE and relies on
COMPILE-FILE-PATHNAME, which tells ECL that the name of a compiled file
called CMP has to be cmp.fasc (vs. cmp.fas which is the real name).
I do not see a simple escape out of this, other than creating ficticious
*.fasc files for every *.fas file in ECL's library.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Ecls-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecls-list
