Re: asdf dependency question

Brian Seitz <[email protected]> writes:

> stated (others have suggested the same situation).  I suspected my own
> heretical additions of last-loaded and last-compiled to be the cause of
> this problem, so I thought I should investigate.  But I tried a version of
> asdf before those were committed and it still had the same problem.

No, I suspect that last-loaded and last-compiled actually are
(partially) masking the problem rather than contributing to it.  I
know what the problem is, and am working on a (by my lights) elegant
solution, which I hope to be able to commit tomorrow (Thursday) and
expect to be able to commit sometime between now and the weekend.

> I have a really slow and probably even more heretical fix for this problem
> that has (operation-done-p ((o operation) (c source-file)) check the
> last-compiled of c against all its dependencies.  But there's probably a
> better way.

It's not giving away too much to admit that I have rewritten the
default operation-done-p method

> It's debatable how much of a bug this is.  It's primarily (only?) a
> problem with redefining macros, but I think LISP developers are wary of

I think it's definitely a bug.  Redefining a macro is exactly the kind
of circumstance that I really want to be able to depend on my
defsystem doing TRT

Thanks for the test case


-dan

-- 

  http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources 


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en