freenode/#lisp - IRC Chatlog
Search
9:50:23
frgo
I am trying to tell ASDF where it can find sources for a system - I am using AllegroCL and ASDF 3.2 .
10:08:38
frgo
well, that's not really a viable option in this case. I am using AllegroCL's stock CLX which comes as a single CLX.fasl file. I have downloaded the sources seprately - but there is no "link" between them.
10:10:53
beach
I don't get it. Are you saying that you can neither control where you put the CLX code, nor put a symbolic link in the directory where ASDF looks for systems, to the directory where you downloaded CLX?
10:12:22
LdBeth
beach: frgo means how to use ACL’s CLX to replace regular CLX as a dependency for certain ASDF systems
10:12:57
frgo
CLX.fasl sits in a predefined directory - I cannot change that. The source sits in another directory. I now want to tell ASDF that the source directory of the system CLX is in my chosen directory.
10:14:52
frgo
I do not use ASDF to load the fasl file. I use (require :clx) and AllegroCL loads its stock CLX.
10:15:48
LdBeth
You just edit the asd file of the project that requires CLX to omit CLX as dependency
10:18:50
frgo
I need to debug AllegroCL's stock CLX. As I downloaded the sources into a directory outside of the AllegroCL installation directory I now need a way to tell ASDF where to find the sources.
10:19:47
ck_
and you're sure that they are compatible? I didn't even know that Allegro offered its sources for download
10:23:15
ck_
but if the implementations differ, how can you sensibly debug one with the sources of the other?
10:32:42
ck_
if you have the sources for that CLX, won't compiling those yourself solve your problem?
10:34:12
beach
frgo: OK, so you want to use a CLX version that is not the one you get by your REQUIRE.
10:34:23
frgo
Now, I want to use SLIME's fantastic M-. capability to find the sources when I am in a backtrace.
10:35:06
frgo
I do have the compiled CLX.fasl file. That comes with a stock installation of AllegroCL.
10:35:46
frgo
Franz Inc provides the sources as a separate download. I downloaded the source separately.
10:38:58
frgo
I thought that I could use ASDF to make the system's fasl and sources to "find each other",
10:39:35
frgo
Now that you mention it - well, I then tried to use the wrong approach to solve that problem.
10:44:11
ck_
I have never tried to augment an existing fasl file with the source information. Aren't those references byte-positions to a specific file?
10:51:15
beach
frgo: SLIME asks SWANK to evaluate a call to FRAME-SOURCE-LOCATION which is implementation specific.
10:51:52
beach
frgo: I suspect the source location, if present at all, must be in the fasl file for it to work.
11:04:32
frgo
-> Connection failure to X11.0 server host.docker.internal display 0: No protocol specified
11:25:08
jackdaniel
frgo: most likely the only part you'd need to compare is dep-allegro and dependants file
14:25:36
akoana
Josh_2: if you're using SLIME, this may help: https://common-lisp.net/project/slime/doc/html/Connecting-to-a-remote-lisp.html#Connecting-to-a-remote-lisp
14:38:31
aoeu512
Are macro(white-box) "adverbs" useful? By adverbs I mean fuctions that take in other functions and then return a modified function. A macro or whitebox adverb looks up the source code of the function and alters it. For example, (replace + (('apply 'debug-apply))) = Creates a new + function that replaces all function calls to use a debug-apply function that prints out its arguments. Is there any theory about these?