libera/#commonlisp - IRC Chatlog
Search
21:30:41
Bike
most of the changes relate to objects. i might try (later) putting in some mop magic so you don't need a defencoding form for each class you want to serialize
21:33:04
Bike
or at least so you can skip all the slot names. i already put something in so defencoding forms kind of work with inheritance
21:36:09
mfiano
I mostly used it for serializing a bunch of octet vectors with a lisp dsl index at the head to find things. game assets and such
5:39:40
drmeister
I dug through the filename/pathname text in the CLHS and I can't find anything that disallows it.
5:45:46
drmeister
The answer may be in this issue: http://www.lispworks.com/documentation/HyperSpec/Issues/iss265_w.htm
5:47:21
drmeister
"even (NAMESTRING (MAKE-PATHNAME :TYPE "LISP")) constructs a plausible looking pathname, ..."
5:55:41
Nilby
(namestring (make-pathname :type "foo"))) => sbcl: error, ccl: ".foo", ecl: nil, clisp: ".foo", etc... so you can do whatever you want because pathnames already suck
6:05:13
Nilby
Meanwhile here in the future, there's two kinds of file names, one that's simple and everyone likes it and can be just a list. Another that includes ipv6 addresses and GUIDs, and nothing really handles fully.
7:35:32
grawlinson
distro packager here, is there any point in symlinking .asd files to /usr/share/common-lisp/systems? it seems to be in Fedora/OpenSUSE/Arch's packaging guidelines but as far as I can tell, Debian doesn't bother with it
7:42:53
semz
grawlinson: The ASDF manual (https://asdf.common-lisp.dev/asdf.html ยง4.2) says it's a common (but outdated?) idiom. I don't think it's strictly required.