Works for me on ASDF.
For load-op and compile-op, times are stored in the operation-times
slot of the component, as accessed by component-operation-times.
Load-source-op should be doing the same, really. I've just added a
method component-operation-time that allows one to do the Right
Thing(tm) wh
Situation:
abcl
there is a newer compiled file than source file
calling load-op on the system with this file causes the fasl to be repeatedly
loaded.
The reason, it appears:
(defmethod perform ((o load-op) (c cl-source-file))
#-ecl (mapcar #'load (input-files o c))
#+ecl (loop :for i :in (i
I realize that the following patch in needed in 1.713. Mark, can you
comment on whether it's always safe to use /___jar__root__file___/
without risk that a host/device will be imported from
default-pathname-defaults when I truenamize it?
- (relativize-pathname-directory p)
+ (relativize
I merged something as 1.712. Please test with ABCL.
Unlike the version that you had going through namestrings of
make-pathnames, it shouldn't have the pitfall of horrors when the
*default-pathname-defaults* supplies an interesting device. Just like
your version, though, it probably supposes that /f
Dear Mark,
thanks a lot for your patch. Your efforts are appreciated.
On 1 May 2010 14:04, Mark Evenson wrote:
> Attached please find a patch which fixes problems pointed out by Carlos
> Ungil when ABCL would catastrophically fail to translate the output location
> for ASDF systems located withi
OK, so ASDF 1.711 is officially our release candidate. Consider the
git master frozen for anything but bug fixes and documentation. Please
use branches for any other development.
My next task is to find someone responsible for every implementation to
1- test it on each supported OS
2- actually com
Attached please find a patch which fixes problems pointed out by Carlos
Ungil when ABCL would catastrophically fail to translate the output
location for ASDF systems located within jar files under Windows.
We've fixed this in the version of ASDF 1.679 which we are planning to
ship as part of a
On 4/10/10 3:25 PM, Mark Evenson wrote:
> On 4/6/10 1:24 AM, james anderson wrote:
>> given:
>>
>> [1] CL-USER(69): (lisp-implementation-type)
>> "Armed Bear Common Lisp"
>> [2] CL-USER(70): (lisp-implementation-version)
>> "0.19.1"
>> [3] CL-USER(73): asdf::*asdf-version*
>> "1.666"
>>
>> asdf fai