On 21 Mar 2018, at 14:09, Robert Dodier wrote:
Thanks for your comments, Robert. I've revised the INFO-INDEX class
and made it a lot simpler (and still working the same). For what it's
worth, I've pasted it below.
I noticed that UIOP:COPY-FILE doesn't seem to behave well if told to
copy a file
Thanks for your comments, Robert. I've revised the INFO-INDEX class
and made it a lot simpler (and still working the same). For what it's
worth, I've pasted it below.
I noticed that UIOP:COPY-FILE doesn't seem to behave well if told to
copy a file to itself -- it clobbers the file. That seems
On Tue, Mar 20, 2018 at 7:30 PM, Faré wrote:
> If your index is just a lisp file,
> why do you even need to subclass cl-source-file, to begin with?
> And if you do, why do you need override any method or initform?
> Let the CL source files be compiled the normal way!
Yes,
Dear Robert and Robert,
here is a complement to Robert Goldman's excellent response.
It includes some style hints for the future of ASDF and its extensions.
>: Robert Dodier
> What I finally settled on is this. When the operation is COMPILE-OP,
> the .info file is copied to same location where
On 20 Mar 2018, at 12:31, Robert Dodier wrote:
Hi, I was asking recently about how to handle a .info file and its
index (CL) in ASDF.
What I finally settled on is this. When the operation is COMPILE-OP,
the .info file is copied to same location where the index fasl will go
(because the index
Hi, I was asking recently about how to handle a .info file and its
index (CL) in ASDF.
What I finally settled on is this. When the operation is COMPILE-OP,
the .info file is copied to same location where the index fasl will go
(because the index has some code to read the .info and it assumes the