freenode/#lisp - IRC Chatlog
Search
9:44:44
xificurC
but to summarize what I hope to have learned from this - macrolet is fine when wanting to expand something in the function-call position (sorry for the improper term, not sure what the correct term is). If one wants to do transformations that require searching for anything else naive code walking techniques will fail in bizarre ways
9:45:40
shka
then you surely noticed how it explicitly states that writing code walkers is challenging
9:48:49
xificurC
shka: yes I noticed. What I might have not explained explicitly is that I don't know how much can I trust a person that says to understand the complexity of the issue and then goes on creating macros that by one's own definition will fail to take that complexity in mind
9:50:51
xificurC
e.g. while I like defmacro!'s g! and o! symbols I don't want to take that shortcut if I'll end up debugging some broken expansion for hours before understanding it's not my bug but the macro's
13:51:30
xificurC
beach: are you an author/maintainer of some CLs? I saw you mention sicl and cleavir?
13:52:12
minion
xificurC: SICL: SICL is a (perhaps futile) attempt to re-implement Common Lisp from scratch, hopefully using improved programming and bootstrapping techniques. See https://github.com/robert-strandh/SICL
13:52:17
minion
xificurC: Cleavir: A project to create an implementation-independent compilation framework for Common Lisp. Currently Cleavir is part of SICL, but that might change in the future
13:54:17
beach
No, no other Common Lisp implementation. However, I was one of the creators of McCLIM, now maintained by jackdaniel.
19:34:02
makomo
xificurC: i just saw the discussion regarding code-walking, it was me who linked the stuff :-)
19:34:30
makomo
xificurC: FWIW, while i think LoL is a great book, i also don't like how he just skips over the code-walking issue in his defmacro/g! and defmacro! macros
19:35:52
makomo
the first time i was reading LoL and came here for help regarding the "brokenness" of those exact macros, i was told there were many before me as well
19:41:33
makomo
"When browsing the text online, you will see the original content, exactly as printed."
20:06:22
makomo
pjb: i think you linked it a few days ago. i took a quick look but can't remember much. i'll check it out :-)
21:02:46
drmeister
I wonder if anyone has insight into an issue I'm seeing with docker and quicklisp - I'm trying to do something unusual.
21:03:25
drmeister
I've got a docker image (docker hub: drmeister/cando) that I'm mounting a ~/.cache and ~/quicklisp/local-projects directory into.
21:04:18
drmeister
These directories are on the host and mounted into the corresponding directories in the docker image.≈
21:05:13
drmeister
Everytime I start the docker container - quicklisp recompiles the systems from the ~/quicklisp/local-projects directory
21:05:47
drmeister
I'm trying to also mount the .cache directory - so that it can use the cached fasls - but that is not working.
21:06:21
drmeister
quicklisp/asdf use time stamps of the source files and fasls to decide if it should recompile something - correct?
21:07:15
drmeister
Hmm - the docker image uses UTC time by default. Maybe it doesn't like that the compiled fasls look like they are from a couple of hours in the future.
21:07:47
drmeister
But - fasls compiled in the future are always better than fasls compiled in the past. Hmmph
21:10:02
akkad
drmeister: you can fix that with updating the /etc/localtime and other /etc/ timezone items to match the hosts
21:11:23
akkad
that way you can avoid installing time related packages, and playing the time difference gam