Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Dodier
Hi, I am resuming my tinkering on the Maxima interface to ASDF. I have bumped into a kind of minor problem for which I don't see a solution. Maxima can read .info files for documentation items. An index file (Lisp) which is created ahead of time (not run time) tells where the items are in the

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Lucien P
On Fri, Mar 16, 2018, 11:25 Robert Dodier wrote: > Hi, > I am resuming my tinkering on the Maxima interface to ASDF. I have > bumped into a kind of minor problem for which I don't see a solution. > > Maxima can read .info files for documentation items. An index file >

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Dodier
Thanks, Robert, that helps a lot. Using ASDF:SYSTEM-RELATIVE-PATHNAME is a big step forward. A follow-up question: Is there a way to know, within a file which is being loaded, whether or not it's being loaded via ASDF? The index file might be loaded via CL:LOAD also. Just to clarify the

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Dodier
On Fri, Mar 16, 2018 at 11:05 AM, Lucien P wrote: > ASDF will put your static file into the FASL location without touching it > then you can find it to load using ASDF:FIND-COMPONENT. One of the > component's slots will have the pathname of the "compiled" file in it, you >

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 13:05, Lucien P wrote: On Fri, Mar 16, 2018, 11:25 Robert Dodier wrote: Hi, I am resuming my tinkering on the Maxima interface to ASDF. I have bumped into a kind of minor problem for which I don't see a solution. Maxima can read .info files for

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 15:03, Robert Dodier wrote: Thanks, Robert, that helps a lot. Using ASDF:SYSTEM-RELATIVE-PATHNAME is a big step forward. A follow-up question: Is there a way to know, within a file which is being loaded, whether or not it's being loaded via ASDF? The index file might be

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Dodier
On Fri, Mar 16, 2018 at 1:59 PM, Robert Goldman wrote: > Another trick you could try is to define a special class of files for the > info files (probably just a subclass of cl-source-file). Then you could tell > ASDF not to move that class of files, by providing a method on

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 17:52, Robert Dodier wrote: On Fri, Mar 16, 2018 at 1:59 PM, Robert Goldman wrote: Another trick you could try is to define a special class of files for the info files (probably just a subclass of cl-source-file). Then you could tell ASDF not to move