Search
Saturday, 9th of June 2018, 1:09:14 UTC
2:42:32
asarch_
One stupid question: what is the name of the exceptions in Lisp?
2:43:22
asarch_
Thank you very much Bike :-)
5:25:12
fiddlerwoaroof
I wish ASDF didn't insist on /s for separating system name components
5:25:29
fiddlerwoaroof
like my-system/subsystem, etc...
6:26:34
beach
Good morning everyone!
6:26:58
beach
jackdaniel: I am not sure that the CLtL2 environment interface is the way to go now that we have CLOS.
6:29:07
beach
jackdaniel: I am also not sure what the right protocol would be.
7:01:43
jackdaniel
beach: how CLOS makes it less useful?
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.
7:14:34
jackdaniel
ah. well, I find it pretty clear as an interface and don't see any need for CLOS
7:14:47
beach
OK. That's fine then.
8:13:31
MichaelRaskin
jackdaniel: well, here CLOS could be useful is if you guarantee some fixed type specifier to correspond to environment
9:10:16
energizer
** NICK energizer_
9:11:50
energizer_
** NICK energizer
10:21:55
random9899
an update for the package lift, not being able to locate it's own config http://dpaste.com/3JDZ8QD
10:23:42
random9899
rosetta-test fails because of it for example....
11:32:06
phoe
today is the first day when I used (declare (special *variable*))
11:59:13
longshi
why is that a special day? (i'm more of a scheme guy)
12:00:25
beach
longshi: Usually, special variables are created using DEFVAR or DEFPARMETER, and they also proclaim the variable special.
12:00:52
beach
longshi: So there is usually no reason for such a declaration.
12:00:56
random9899
finally git cloned informatimago too
12:02:35
phoe
this time I wanted to declare a variable special only locally, without creating a global binding
12:08:20
beach
longshi: So what brings you to #lisp?
12:09:04
longshi
I started reading Practical Common Lisp, installed sbcl
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:12:19
longshi
I believe so, yeah--i'm still an amateur though, i'll start BA in CS this October
12:12:37
longshi
btw, now that we're talking, a question:
12:12:41
random9899
ya and this way i get the reports http://dpaste.com/3B1MR1F
12:12:54
longshi
so i went through cl-koans by google
12:13:32
longshi
would you recommend it as an intro to a language or is there something better?
12:13:52
longshi
(i like them koans, i learn faster when it's interactive)
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:14:47
beach
I haven't looked at the koans. Do you have a link?
12:15:04
longshi
Especially comparing library situation of CL and various schemes
12:15:29
longshi
beach: here https://github.com/google/lisp-koans/
12:15:30
phoe
beach: I assume https://github.com/google/lisp-koans
12:15:50
beach
longshi: Let me have a look...
12:16:28
beach
longshi: Oh, lots of unconventional code in there.
12:17:03
beach
longshi: I am looking at dice-project.lsp (the first one I clicked on)...
12:17:59
beach
longshi: Wrong number of semicolons in comments. Parentheses by themselves on a line. Wrong indentation.
12:18:38
beach
Looking at control-statements.lsp...
12:19:18
beach
For one thing, Common Lisp "statements" are called "forms" in most situations.
12:19:50
random-nick
also, why .lsp instead od .lisp?
12:20:05
beach
There should not be a newline after (and
12:21:32
beach
Wrong indentation, wrong number of semicolons.
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:33
kenanb
longshi: I remember cl-ppcre being a frequently suggested code reading exercise
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:23:08
longshi
yeah, i use (1+ x) in scheme too
12:23:13
beach
longshi: I am sorry to say that there are many problem in that code.
12:23:46
longshi
i didn't properly read it all before responding
12:25:51
beach
Initialization of lexical variable in LET that is then immediately assigned to.
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.
12:47:24
specbot
http://www.lispworks.com/reference/HyperSpec/Body/f_car_c.htm
12:47:25
specbot
http://www.lispworks.com/reference/HyperSpec/Body/a_cons.htm
12:48:01
jackdaniel
longshi: if you need to look something up I recommend using l1sp.org
12:48:05
longshi
didn't know that existed
12:48:10
jackdaniel
it has lookup into clhs, pcl and some other resources
12:48:26
beach
longshi: It's basically a HTML-ized version of the standard.
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:08:22
beach
What kind of information should the liveness include?
13:08:38
beach
Is there any information missing that I should add?
Saturday, 9th of June 2018, 13:09:14 UTC