freenode/#lisp - IRC Chatlog
Search
6:26:58
beach
jackdaniel: I am not sure that the CLtL2 environment interface is the way to go now that we have CLOS.
7:13:26
beach
jackdaniel: 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.
8:13:31
MichaelRaskin
jackdaniel: well, here CLOS could be useful is if you guarantee some fixed type specifier to correspond to environment
10:21:55
random9899
an update for the package lift, not being able to locate it's own config http://dpaste.com/3JDZ8QD
12:00:25
beach
longshi: Usually, special variables are created using DEFVAR or DEFPARMETER, and they also proclaim the variable special.
12:02:35
phoe
this time I wanted to declare a variable special only locally, without creating a global binding
12:09:57
longshi
i'm still more used to (r6rs) scheme ways of doing things, but it's lisp after all, similar enough
12:10:37
beach
Is it just out of curiosity, or are you planning to write some code using Common Lisp?
12:14:25
longshi
beach: this wasn't to precise--yes, i think i will write code in CL once i know it well enough
12:17:59
beach
longshi: Wrong number of semicolons in comments. Parentheses by themselves on a line. Wrong indentation.
12:21:36
kenanb
longshi: if you are coming from scheme, you can probably just read some good library code along PCL to learn the language.
12:21:49
jackdaniel
random-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:44
beach
Use of get- and set- prefixes. We have a few of those for historical reasons, but they should be avoided in new code.
12:27:13
beach
longshi: 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:54
kenanb
longshi: 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.
13:07:54
beach
In SICL, I plan to represent code in a code object, as written here: http://metamodular.com/code-object.pdf but I have some questions...
13:09:38
beach
In what situations should the NEXT debugger command go from the end of a form to the BEGINNING of the next form to be evaluated?
13:10:41
beach
I am thinking if two forms are just sequential like this: (form1 ...) (form2 ...) then from the end of (form1 ...) the NEXT command should go to the end of (form2 ...).
13:12:01
beach
But maybe if there is a big gap between the two forms, like in ((((.... (form1...)))) (form2 ...)) then perhaps go from the end of (form1 ...) to the beginning of (form2 ...).
13:12:28
phoe
beach: the three commands that I know from debuggers are STEP-INTO, STEP-OVER, STEP-OUT.