21:33:25jmercourisI'm looking at Qlot right now, at this function specifically https://github.com/fukamachi/qlot/blob/master/install/quicklisp.lisp#L16
21:33:34jmercourishow does it fetch the installer???
21:33:51jmercourisit is supposed to call http-fetch, but it is just not actually fetching..
21:34:46jcowanHow can I find standard functions that return two values, either the result or #t if there is a result, or #f #f if there isn't one? hashref works like this, but what else
21:38:05jmercouriscan anyone confirm if ql:http-fetch is working on their machines as I expect it to be for myself?
21:38:45jmercourisI also tried the variation: (ql-http:http-fetch "http://beta.quicklisp.org/quicklisp.lisp" #P"/Users/jmercouris/Downloads/quicklisp-JBCUCRBI.lisp")
6:33:26phoebeach: regarding the shortness of the condition system, the original isn't very long either - see http://www.nhplace.com/kent/CL/Revision-18.lisp
6:36:21phoethe largest bloaters, size-wise, are all the DEFINE-CONDITIONs. And the largest bloater, cognition-wise, IMO, is HANDLER-CASE with its :no-error case
6:38:18phoeas Stas once said, a condition system is easy; dynamic variables, UNWIND-PROTECT, and GO/RETURN-FROM are hard
6:42:37beachphoe: I see, yes. We have already taken care of the hard parts in SICL then.
6:49:01beachphoe: Would you like to work on SICL with us?
6:50:06phoebeach: I will possibly be able to contribute a thing or two, sure. My main focus will be CLUS as soon as my book is finished, but I think I'll be able to add this or that to SICL in meantime.
6:50:38beachSounds great! Do you have a preferable subject you would like to dig into?