libera/#commonlisp - IRC Chatlog
Search
16:06:27
didi
Is this expected? I have the following file https://paste.debian.net/hidden/00bb7521 . I then eval in another package (defvar *bar* foo:*foo*) and (eq *bar* foo:*foo*) => t. All is good. But, if I compile the file in SLIME using C-c C-k, (eq *bar* foo:*foo*) => nil. I'm using SBCL.
16:11:08
gilberth
It is. When you compile and load that file foo:*foo* is set again with DEFPARAMETER to a new (3 . 4) different from the previous one that *BAR* still has.
16:13:02
didi
So I need to think of another way of setting a sentinel that I can test using EQ and that will survive recompilations.
16:14:12
gilberth
DEFVAR only sets the variable when it has no value yet, while DEFPARAMETER always sets the variable.
17:29:35
Josh_2
adding it as dependency broke my build pipeline because it depends on sqlite... :sob:
17:57:06
semarie
Posterdati: could you define "broken" a bit more ? which lisp implementation ? which error ? etc...
18:16:03
ecraven
is there a generic database library, that can do sql queries to different database backends?
18:25:39
jjnkn
when i tried cl-dbi i encountered an issue with executing multiple sql statements at once; i wanted to run an sql script, so i just read the whole file and tried to execute its contents but cl-dbi signaled an error
21:23:01
gendl__
Hi, is it true that Bordeaux-threads doesn't have shared read-locks and write-locks, where multiple readers can hold the lock at the same time as long as no writer holds the lock? You'd have to implement those yourself?
21:26:20
gendl__
(i know there's a pretty formulaic way to build readlocks/writelocks given basic mutexes and condition variables)
22:16:30
fe[nl]ix
gendl__: that's correct. there's a feature request open: https://github.com/sionescu/bordeaux-threads/issues/77