libera/#commonlisp - IRC Chatlog
Search
16:52:36
Xach
Krystof: thanks. block names were my first thought but the env object I have is a bit more opaque to me than SBCL's
16:57:07
dieggsy
with slime/sly is there no way to make sure all output is shown in the repl buffer (as opposed to some going to the inferior lisp buffer) ?
16:58:52
scymtym
Xach: the log4cl library must have something like that but i doubt it is even remotely standard-ish
17:02:42
Xach
Allegro would be most useful to me in fact. Time to scrape around the env object a little more.
17:59:04
jackdaniel
(1+ most-positive-fixnum) ways for making repl unusable: (setf *print-right-margin* (1+ most-positive-fixnum))
18:24:33
pjb
jackdaniel: it's a non-negative integer, so (1+ most-positive-fixnum) is perfectly conforming.
20:07:07
Shinmera
the new update argument also allows posting four pictures, and very large gifs or videos.
3:28:11
dieggsy
or, is it possible to run a lisp function defined in the current environment in a separate process
3:30:16
dieggsy
we basically have some legacy build script written in bash and lisp, and i thought "why not just do this in only lisp", but then was like "oh wait because it compiles and loads a bunch of stuff", so I'm trying to... both integrate the code but also separate it from the current environment when it runs ? if that makes any sense at all
4:19:19
dieggsy
ludston: thanks, though that largely concerns launching external programs as a process, and I want to run some lisp as a process
4:19:44
ludston
If for whatever reason you need to sandbox some function in another process, you probably just spin up a new lisp instance with --load "(my lisp code here)"
4:22:14
dieggsy
....i believe process-run-function is spawning a new thread, but i don't completely understand allegro's multiprocessing documentation
4:23:14
ludston
Use bordeaux-threads. It's the defacto standard library that most of us for multithreading
4:24:48
dieggsy
I've used Bordeaux threads in the past, but unfortunately I'm trying to stick with what's built in because of uhhh
4:25:51
dieggsy
though come to think of it i think some parts of the code do use bordeaux threads so maybe i can just sneak that into this bit as well
4:28:45
ludston
I work on a really horrible, old code-base (not lisp) too. In my experience it is better not to get stuck in the "not invented here" mindset and use the library/make the sweeping change that you are afraid to make.
4:30:28
ludston
The worst thing that can happen is your experienced code-reviewer says no and then you learn why.
4:31:39
dieggsy
well, the worst that could happen is "why" is just "that's not how we do it" and well ok you're the boss heh
4:38:55
dieggsy
fe[nl]ix: STScI, only like a month in. (employer if you are reading this i am sincerely having a blast) jajaja