Search
Sunday, 25th of July 2021, 21:15:24 UTC
21:24:40
edgar-rft
let's all our symbols have surnames
21:25:25
lotuseater
(defvar *symbol-mc-symbol* ...)
21:46:19
jcowan
Package names are like surnames
21:50:56
lotuseater
are then the double colon not exposed symbols package::symbol the childrens the world shall not know about? ^^
21:52:25
Alfr
And what about apparently uninterned symbols?
22:00:40
moon-child
jcowan: in j, package names go after explicitly qualified symbols, rather than before
22:00:57
jcowan
Eh, so do surnames in Hungary, China, Japan, ...
22:02:58
moon-child
jcowan: that's backwards
22:03:32
jcowan
Never tell a Hungarian he is backwards. You can tell a Chinese that, but they will loftily ignore you.
22:26:55
edgar-rft
this is what you could tell to hungarians -> https://www.youtube.com/watch?v=C1Sw0PDgHU4
3:01:19
beach
Good morning everyone!
7:01:44
_death
minion: memo for scymtym: you're right, there is :drag-callback.. it was something different that I can't recall at the moment
7:01:51
minion
Remembered. I'll tell scymtym when he/she/it next speaks.
7:29:17
Qwnavery
Hello, if someone has a moment to spare; I'm having some trouble getting quicklisp to recognize foreign libraries
7:29:57
beach
Just ask your question.
7:30:14
Qwnavery
It can't load libsqlite3 and sqlite3 for clsql library
7:31:05
Qwnavery
I've searched and nothing comes up. I'm unsure if it's a fault of musl libc
7:31:54
Qwnavery
- Using Voidlinux + musl, sbcl + quicklisp
7:32:40
beach
I wasn't aware that Quicklisp could do foriegn code at all.
7:33:02
Qwnavery
It may just be the clsql library then
7:33:52
Qwnavery
Apologies, it is the library clsql
7:34:32
_death
if you have the libsqlite3 shared library somewhere, you can check that the loader/cffi find it, see /etc/ld.so.conf and cffi:*foreign-library-directories* respectively
7:36:35
Qwnavery
https://pastebin.com/vZRmLFwg
7:36:56
pve
Qwnavery: does (quicklisp:quickload "sqlite") work?
7:37:36
_death
oh right, ancient uffi.. well, it has *foreign-library-search-paths* according to that form
7:37:59
Qwnavery
pvi it's installing, is there any reference for it or is it apart of the standard lib?
7:39:51
Qwnavery
https://common-lisp.net/project/cl-sqlite/ is this the "sqlite" package?
7:40:19
pve
Qwnavery: can you do (defparameter *DB* (sqlite:connect "mydatabase.db")), for instance?
7:40:42
pve
Qwnavery: yes, that's the one
7:41:25
Qwnavery
pve: it appears to be valid
7:42:24
pve
Qwnavery: then it's probably clsql that's causing trouble
7:43:10
Qwnavery
Yeah, is there any tangible performance benefit for using clsql for sqlite over sqlite?
7:43:35
Qwnavery
if not then it's probably not worth trying to get foreign librarys working that's all
7:44:11
pve
Qwnavery: both of those rely on foreign libraries
7:44:56
Qwnavery
pve herm. ok. well sqlite is working so I'll stick with that I guess.
7:45:37
pve
Qwnavery: you can probably forget about clsql for now
7:46:56
Qwnavery
you can tell, yeah I'm new. Apologies for being a nuisance. Thanks for your time. Really appreciated.
8:40:45
lotuseater
good morning fellow lispers
8:58:17
pl
ASDF can do some foreign code, and what ASDF can, QL can
8:58:58
pl
And hello, I haven't been active here long, I feel... (Leenode migration doesn't count)
9:09:18
pl
Anything particularly noteworthy in changes to common libs, implementations? I feel a bit behind on news
9:10:54
beach
pl: The WSCL effort is well on the way: https://github.com/s-expressionists/wscl/tree/main/wscl-issues/proposed
9:12:40
pl
Ooh, nice. Especially the part where it apparently codifies current real world behavior
9:14:01
beach
That's the main idea with WSCL, i.e., do not invent anything that the main existing implementations don't already do.
9:14:30
beach
So, just transfer reasonable and agreed-upon behavior to the specification.
Monday, 26th of July 2021, 9:15:24 UTC