freenode/lisp - IRC Chatlog
Search
1:17:38
knusbaum
Looks like read-sequence will block until the sequence is filled or EOF. Is there a way to just read a bounded chunk from a stream, returning whatever's available, like POSIX read(2)?
1:36:12
knusbaum
My problem is regarding usockets. I have to be careful not to get into a situation where I'm blocked on a client who's never going to send anything, but I don't see how to do that without checking for available data before each call to read-byte.
1:47:04
knusbaum
Hmm. Looking for something in usockets to do that. Or should I be using something else?
2:37:02
emaczen
What is a file format for writing persitent objects? I was thinking (type :id id :slot-name slot-value :slot-name2 slot-value2 ...)
2:38:03
emaczen
Also, what would a typical access entail w.r.t opening the file reading in the data etc...
3:01:21
diegs_
Anyone used the dbus library? I'm trying to replicate this: https://gist.github.com/therockmandolinist/f2d3fbcde760435fd1ca98c83c335d4d functionality based on https://github.com/death/dbus/blob/master/examples/notify.lisp that example, but rather unsuccessfully
4:09:39
emaczen
Can someone point me to or give me an overview of how object persistence works, maybe even beyond the MOP?
4:35:04
beach
emaczen: I am guessing it is pretty messy in a system (OS + Common Lisp implementation) that was not meant for it in the first place.
4:36:54
beach
emaczen: You may consider looking at this one: https://github.com/robert-strandh/Clobber
4:49:15
White_Flame
emaczen: the biggest issues to deal with are serializing function objects and dealing with multiple references to shared objects
4:49:49
White_Flame
different libraries deal with such things in different ways. The only "standard" way persistence happens is saving your lisp image, which isn't even in the spec
4:54:21
beach
emaczen: If you can describe your needs, that might make it easier to give you advice.
7:22:24
jackdaniel
emaczen: cl-store is a very versatile and complete library for serialization, reading its sources may be beneficial
10:19:55
rk[ghost]
that brings up an interesting thought.. what do you all use for serialization of function objects?
11:08:25
_death
generally you avoid serializing those.. but see http://www.discontinuity.info/~pkhuong/common-cold/
11:40:26
phoe
generally you serialize those by (if at all) capturing their source code at compile time and storing the source code, then compiling it again during deserialization