17:26:40sigjuiceI have several versions of alexandria in ~/quicklisp/dists/quicklisp/software from continued use of (ql:update-dist "quicklisp"). How does quicklisp know which one to use?
17:26:55Xachsigjuice: it uses only the one indexed by the metadata files
17:27:08Xachsigjuice: you can remove the old copies with (ql-dist:clean (ql-dist:dist "quicklisp"))
17:27:34sigjuiceXach: thanks! that was going to be my next question :)
17:27:37Xachsigjuice: the metadata files are in ~/quicklisp/dists/quicklisp/installed/
23:10:13ShinmeraMy slide show app is coming along. https://www.youtube.com/watch?v=bB0BlN8ORiA&feature=youtu.be
23:25:29hjudtare there any best practices naming accessors? if i have a class "box" with a slot "id", should i call the accessor box-id or simply id? is there any advantage doing the former?
23:26:10Bikemight avoid a collision with something
23:28:55whomanShinmera: how come you dont use autocomplete like M-/ ?
23:29:03whomanalso, are you still working on trial ?
23:31:39Xachhjudt: I find it useful to think of the protocol of generic functions first, and then use defclass to fill in the easy blanks of specific methods. in that context it doesn't make sense to name the generic functions with the class name (usually).
0:24:23didiWonder: Why isn't the syntax of `let' the same of `setf'? i.e. (let (a a-value b b-value) ...)
0:26:11fiddlerwoaroofdidi: clpjure does that, it's a bit annoying because it's more difficult to delete a binding/value pair
0:31:09Bikei don't think there's much particular reason either way. of course, if you do write a let like that it's short for ((a nil) (a-value nil) (b nil) (b-value nil))