20:01:25XachJosh_2: (asdf:load-asd "/path/to/file") I think. Although I note that I just tried that on a bogus pathname and it returned something, so I don't know what to expect any more.
20:22:45dimfor people who want a graph lib in CL, maybe that's a good candidate
20:31:32pjbphoe: actually if you have a graph that knows its list of nodes, we don't need to walk the graph, just process the list of nodes (and we have to). On the other hand, if the graph is connected, and we only have one "root" node, then we need to walk it.
0:28:18fiddlerwoaroofSpeaking of which, nyef used to be really active here and in #sbcl, but I haven't seen them around in a year or so
1:06:10Josh_2am I missing something here because unwind-protect isn't shutting the socket when test crashes Q_Q https://plaster.tymoon.eu/view/1109#1109
1:24:26dloweThe documentation says that it makes TCP less reliable, but in practice I've never had trouble with it
1:26:32Josh_2Stupid thing, the address is still in use when it crashes *sigh*
1:26:54fiddlerwoaroofHmm, one thing you have to be a bit careful about is the stream keeping things open
1:27:46fiddlerwoaroofI don't know if this is relevant here, but I've had issues with drakma where I eventually run out of fds when I do (drakma:http-request "///" :want-stream t) because, unless I close the stream, the socket never gets released.
1:27:50Josh_2I have added another unwind-protect hopefully that'll fix it
1:39:26fiddlerwoaroofI have a suspicion that additional unwind-protects won't make a difference, unless there's an error in establish-tcp-connection
1:40:52Josh_2fiddlerwoaroof: I think you got it right
2:56:16r13lis it correct that there’s no way to kill processes started by uiop:run-program (e.g. if one receives a SIGTERM oneself)? maybe i should try to add support for uiop:launch-program to inferior-shell …
7:00:38madrikI've got to the point where I can ask my system which client IP made how many connections; what domains has a given IP visited frequently; etc.
7:05:19madrikIn abstract, wasn't this one of the motivations in the birth of SBCL -- that its ancestor, CMUCL, had a rather involved bootstrapping procedure to build it?
7:09:37beachWe are taking it one step further by bootstrapping CLOS first, rather than last, as is common with implementations that were started before CLOS was part of the standard.
7:10:35madrikWouldn't that be very hard -- going CLOS-first, I mean?
7:11:14beachHard enough that we think it deserves a paper. :)
7:13:25beachThere is this widespread idea that bootstrapping has to be done from a subset of the language to the full language in well defined increments.
7:14:10beachBut that is obviously not the case if you bootstrap on an existing conforming Common Lisp implementation. Because then, you already have the full language at your disposal.
7:14:53beachHaving said that, I should add that the procedure for doing it is pretty involved, mainly because of the way that Common Lisp defines compilation differently from other languages.
7:16:08madrikbeach: Sounds challenging but rewarding.