22:49:57rdhXach, wow thank you for that guide, that makes it much more clear.
22:50:17moldybitsi don't know if this is better, but at least it's more natural in clos to distinguish actions by how you name the function as opposed to letting the objects provide the context. (concatenate "a" "b") => "ab" (+ "19" "23") => "42"
22:51:14didimoldybits: This is a good way to emphasize the generic function.
2:45:40aethMissing commas are pretty annoying. You wind up trying to access a variable that doesn't exist because the macro author only tested the macro with outer variables having the same name as the macro variable.
2:47:04aethThen you use foobar instead of foo and see the issue right away.
2:52:16LdBethCan someone explain what's "safe call" in CLHS
2:52:39LdBethOr give an example of "programmer code"
4:35:46beachasarch: You rarely need to use RETURN-FROM. The usual way is what Xach told you.
4:36:48beachasarch: If you find yourself using RETURN-FROM a lot, it might be that your programming style is not that great.
4:37:21aethI'm not sure if I've ever used return-from. Maybe once. It's very rare.
4:38:16no-defun-allowedWorks if you're doing something like a tree-traversing EVERY.
4:38:17beachOccasionally, in a loop, when the final value becomes known, it can be a good solution.
4:38:51asarchWell, that's for a GTK+ call back to do OpenGL rendering operations
4:39:58asarchIf a function need something like (foo ... (lambda (x y) ...)), how could I put (lambda ...) in a function and the pass that function to (foo ...)?