7:01:43jackdanielbeach: how CLOS makes it less useful?
7:13:26beachjackdaniel: What I am saying is that the interface described in CLtL2 is a bit twisted because it does not take advantage of generic functions. I think we can do better than that now.
7:14:34jackdanielah. well, I find it pretty clear as an interface and don't see any need for CLOS
12:21:32beachWrong indentation, wrong number of semicolons.
12:21:36kenanblongshi: if you are coming from scheme, you can probably just read some good library code along PCL to learn the language.
12:21:49jackdanielrandom-nick: lsp was one of agreed extensions in the early CL days (think about MS-DOS for instance). now .lisp seem to have took over, but there are still codebases with .lsp
12:22:33kenanblongshi: I remember cl-ppcre being a frequently suggested code reading exercise
12:22:44beachUse of get- and set- prefixes. We have a few of those for historical reasons, but they should be avoided in new code.
12:25:51beachInitialization of lexical variable in LET that is then immediately assigned to.
12:27:13beachlongshi: So if you want to look at the koans, you had better be careful not to pick up some of the bad habits in that code.
12:34:54kenanblongshi: also, maybe not many would agree with me, but I think Hyperspec is way more than a reference. It is a great resource to learn the language once you are familiar with the basics.