18:13:06fourierthis is when what i'll continue to use...
20:43:16_deathsince you're asking for style advice, my advice is to not care about functions being used only once
21:04:05jasomI don't care about functions being used only once; I'd much rather read (frobnicate-the-foo) than 50 lines that aren't obvious that they frobnicate the foo. However I still think return-from is fine IF the structure of your body doesn't lend itself to e.g COND
21:04:57phoehow do I update a single dist in quicklisp?
21:07:12jasomphoe: "quicklisp" is a dist; ironclad is a system in the quicklisp dist.
21:07:39_deathjasom: I don't have a bad response to return-from, but following the one-function rule usually shows the better way that happens to eliminate it..
21:07:46jasomphoe: if you want finer grained version dependencies, either create your own dist or try something like qlot
21:08:36_deathphoe: I would clone it into local-projects
21:08:47jasomphoe: (ql:update-dist "quicklisp") <-- will update *everything* in quicklisp, *or* drop a newer version of ironclad into local-projects
21:09:03phoejasom: I want to explicitly upgrade only ironclad.
21:09:09phoeso I think I'll clone it into local-projects then.
22:26:23JuanDaughertydo I correctly understand planetlisp, cliki, and whatever ql gets to be the massed lisp greatness at this point, the equiv of hackage, et al.?
3:03:00loke`I'm not sure if :HOME is portable though
3:03:28loke`The glossary entry doesn't say much on the subject: http://www.lispworks.com/documentation/HyperSpec/Body/26_glo_v.htm#valid_pathname_directory
4:53:38atgreenI get a "Heap exhausted during garbage collection" when I try to (ql:quickload 'lisp-binary). sbcl 1.3.5 on Fedora x86_64. Any ideas? How can help debug?
4:58:22atgreenhmmm... I updated quicklisp and lisp-binary was removed. maybe there;s a reason!