libera/#lisp - IRC Chatlog
Search
15:06:05
Josh_2
When connected to a remote lisp image can I get output to from functions like trace to go into my sly repl instead of having to view it with journalctl?
15:18:54
rain3
then why doesn't it output to the repl when you actually trace the functions? check the value of *trace-output* during those funcalls
15:32:31
rain3
This variable controls the global redirection of the the standard streams (*standard-output*, etc) to the REPL in Emacs. https://joaotavora.github.io/sly/
15:44:41
Josh_2
https://plaster.tymoon.eu/view/2567#2567 how do I fix this?? Getting an condition telling me that urandom was shut by save-lisp-and-die...
16:01:30
rain3
does that error happen when you load a fresh sbcl image and quicload ironclad and eval (ironclad:random-bits 13) ?
16:02:02
xaltsc
Hey, having used macros only in LaTeX and, to a lesser extent, in C, I had a really bad opinion of them. Now that I'm learning several Lisp dialects, I see that they are an important idiom, yet, I still see them as a bad programming practice, quite antiquated, just like gotos. Can someone explain me why I am wrong ? Thanks :D
16:04:53
dash[m]
xaltsc: It's a tradeoff of power vs readability. Lisps tend to be biased towards power/flexibility instead of towards readability/auditabilty
16:06:55
Josh_2
There is nothing inherently dangerous about a macro.. in fact I would argue that lots of the time its more dangerous to *not* use them
16:07:25
Josh_2
if you find yourself writing the same piece of code over and over and over you are more likely to make a mistake by doing that than hiding that piece of code behind a macro.
16:08:07
rain3
xaltsc: lisp macros don't operate on text, they operate on the abstract syntax tree of the program . so it's programming the program itself
16:09:39
dash[m]
Josh_2: I recommend this classic essay. http://www.erights.org/data/irrelevance.html