libera/#sicl - IRC Chatlog
Search
12:05:02
beach
I have not seen any such discussion. And I haven't looked very hard into pathnames myself.
12:09:32
yitzi
Yeah, I am trying to remove absolute pathnames that come from source references in Clasp. Need to do so for a redistributable binary. I am suspicious I'll have to add some implementation specific keys to translate-pathname.
12:10:21
beach
Though, now that I think about it, specifying &ALLOW-OTHER-KEYS would not be the same as allowing other keys.
12:11:04
beach
Specifying &ALLOW-OTHER-KEYS would mean that any keyword argument could be given, including some that are not supported by the implementation.
12:11:42
beach
Whereas "allowing other keyword arguments" might just mean that the set is still fixed, but it may be larger than what is mentioned in the standard.
12:16:49
mfiano
I would parse that as the set is of undefined size, meaning it could be fixed or allow anything.
13:17:38
yitzi
beach: Clasp has an ASDF groveler that we use when running under SBCL to extract the source files for Cleavir, etc. I've had to rewrite it to account for systems that have :if-feature style feature expressions. Its not in Clasp main branch yet because the branch is still experimental. Maybe useful for SICL though. https://gist.github.com/yitzchak/0c7a7302c04391787d26a59336c3a1f1
13:20:29
beach
yitzi: Thanks. Anything in particular that made you think about SICL for this library?
13:22:28
yitzi
I seem to recall SICL needing to use ASDF systems from the host that might be different in SICL eventually. I could be just thinking of when I was trying to load the sequence functions though. Its been a while since I bootstrapped SICL.
13:26:45
beach
It needs to create its package based on the host Common Lisp system. And since I use host packages during bootstrapping, I had to create the same package in two different ways, one for the host Common Lisp system, and one for SICL.