freenode/#lisp - IRC Chatlog
Search
8:41:59
beach
didi: Since you are reading CLtL2 and since we discussed when functions are "looked for", check section 8.5, page 209. There is a function FUNCTION-INFORMATION that is not in the Common Lisp HyperSpec, but basically the compiler of every implementation must use something similar to find out what a name in a function position means.
8:49:48
schweers
do I read the hyperspec on aref and bit correctly, that the standard does not specify what happens when I attempt an out ouf bounds access? sbcl seems to throw an sb-int:invalid-array-index-error. I guess it depends on the debug optimizations?
8:52:18
beach
schweers: It also doesn't specify what happens if you give something other than an array to AREF.
8:54:43
beach
The fact that there are so many undefined situations in the Common Lisp HyperSpec is the reason I started the WSCL (pronounced "whistle") project.
8:56:27
beach
I am repeating it for the benefit of those #lisp participants who didn't see it that time. :)
8:59:44
pierpa
Duh. Thanks for the reminder. I was already watching the project but I had forgot about it :(
9:18:55
beach
flip214: For WSCL? My current thinking is to avoid new functionality. A good existing Common Lisp implementation should already be a WSCL implementation, or at least nearly so.
9:21:39
beach
schweers: At the moment, I haven't done anything. But I don't intend to add new functionality. I only plan to specify many of the things that the Common Lisp HyperSpec leaves unspecified. And it should be such that the most common implementations already specify those things in a reasonable way.
9:22:33
schweers
maybe I didn’t make clear what I meant. The standard doesn’t specify what happens when aref is given an out of bounds index. You specified what should happen in WSCL?
9:23:39
schweers
And you only specify behaviour, which at leas one existing implementation already does? For instance, as sbcl throws an error, you might specify that an error should be thrown?
9:24:40
beach
[errors are "signaled" in Common Lisp. Not thrown.] Sort of. I do not plan to check whether at least one implementation does what I want. So it might be the case that for a few cases, no implementation does the right thing.
10:24:44
beach
In fact, if someone could help me set up the dpANS files so that I could do a single `pdflatex' to compile it, then that would help immensely.
10:25:19
beach
Also, someone pointed out that I am not using the most recent version of dpANS, which I didn't know. I would like to do that of course.
10:34:08
pierpa
Perhaps it would be easier to start from the CLHS? It should be way easier to reverse engineer
10:52:21
beach
pierpa: TMA is right. The Common Lisp HyperSpec is copyright by LispWorks and they do not allow derived work.
10:53:26
beach
shka: Doesn't matter much. I mean, phoe has already removed that problem essentially, by creating CLUS.
15:02:14
Xach
I think I use it too little to solve printing problems and that is something to correct!
15:03:46
Shinmera
Xach: I think I found a quite nifty use case for it in my GLSL toolkit: https://github.com/Shirakumo/glsl-toolkit/blob/master/printer.lisp
15:04:14
Shinmera
Though I use a preprocessing step to turn ~o into ~/ORG.SHIRAKUMO.TRIAL.GLSL::%FORMAT-OBJECT/, since that's quite a mouth full.
16:10:09
bl1nd
I want to learn clojurescript. Should I learn clojure before? Should I even learn another dialect of lisp before Clojure?
16:12:11
Shinmera
This channel is for Common Lisp, so you will be told to learn Common Lisp, regardless of your interest in Clojure.
16:12:18
schweers
bl1nd: note that this channel is about common lisp, not the whole lisp family. Nevertheless I suppose learning clojure first will make your life easier.
16:21:22
schweers
not a problem. I guess there are channels dedicated to clojure and clojurescript. Maybe you should ask there