freenode/#lisp - IRC Chatlog
Search
8:56:57
beach
RPLACA and RPLACD should be considered low-level functions to be used mainly by the person creating the Common Lisp system, just like SETQ.
10:28:38
splittist
seok: have you read https://www.common-lisp.net/project/asdf/asdf.html#Configuring-ASDF ?
11:07:01
pjb
moon-child: rplaca is a function; (setf car) is a function too. (let ((cs (list (cons nil nil) (cons nil nil)))) (values (mapc #'rplaca cs '(1 2)) (mapc #'(setf cdr) '(44 55) cs))) #| --> ((1 . 44) (2 . 55)) ; (44 55) |# your choice.
11:08:07
no-defun-allowed
Nope, Clozure does not implement (setf cdr) as a function, and that is allowed somewhere in the standard.
11:09:37
no-defun-allowed
(setf getf) would most likely not be a function, for example, as it might push a new property into the place without modifying list structure.
11:11:05
pjb
moon-child: however, it looks like (function (setf car)) is not conforming: implementations could have no such function, and just hack setf, like for defstruct accessors.
11:12:11
pjb
moon-child: https://termbin.com/27m4 ; so you can see that you have to use rplaca when you need a function.
16:40:53
MrtnDk[m]
minion: memo for jcowan: I wonder what "idiotic mysticism" is then. Can thou please elaborate on that phrase, please, thank you.
19:03:16
thomasb06
Hello. Currently, I'm trying to install Ulubis, and I get this backtrace: https://x0.at/URP.log
19:14:15
Bike
i'm not familiar with ulubis, but it's hard to imagine that log helping. did it really not even give you an error code?
19:21:24
thomasb06
it's a window manager so I should run it from console mode, but the only trace I get is in this file
19:22:11
Bike
https://github.com/malcolmstill/ulubis/blob/master/ulubis.lisp#L139-L141 looks like you're supposed to be getting a backtrace, but evidently not
19:23:16
Bike
print-backtrace prints to *debug-io* whereas that format will print to *standard-output*. maybe the log is only getting the standard output.
19:24:23
Bike
i guess you could try replacing the print-backtrace call with (let ((*debug-io* (make-two-way-stream *standard-input* *standard-output*))) (trivial-backtrace:print-backtrace e)), and then it will print the backtrace to standard output as well.
19:28:24
thomasb06
ah, let me have a look. (it doesn't show but I'm on a sugar crash... had a huge patisserie few hours ago and obviously it was more sugary that what I'm used too)
19:34:29
thomasb06
so I've put `(trivial-backtrace:print-backtrace e :output *standard-output* :verbose t)` and now I recompile
19:42:38
fiddlerwoaroof
luis: one thing that would be really useful on macOS is support for the @executable_path, @loader_path and @rpath variables, although I think this would also need implementation-level changes