freenode/lisp - IRC Chatlog
Search
0:48:14
edgar-rft
theemacsshibe[m], a few more documents are linked in the "Reference" section of https://en.wikipedia.org/wiki/Common_Lisp_Interface_Manager
0:49:33
theemacsshibe[m]
i'm just trying to write some simple GUI applications and honestly most of the background crap goes over my head
1:00:35
drmeister
It says when the second argument is t: Returns a documentation string specialized on the class of the argument x itself. For example, if x is a function, the documentation string associated with the function x is returned.
1:01:20
Bike
the second argument of documentation is only not t when the first argument is a name rather than a thing
1:03:34
Bike
in clasp functions don't actually have docstrings, so if you have like (lambda () "docstring" nil) there's no way to get at the string, as it's destroyed during compilation
1:03:34
drmeister
Peter Seibel's "manifest" system doesn't work on Clasp - but parts of it - most importantly "toot" does.
5:13:01
beach
theemacsshibe[m]: The #clim channel will answer questions about CLIM and McCLIM. I usually hang out there, but I am traveling at the moment. I'll be back online on Wednesday.
5:20:39
beach
Also, scymtym is working on the reader (called Eclector) which used to be part of SICL, but that is now in a separate repository.
5:22:25
beach
I am trying to extract "modules" from SICL into separate repositories as much as is reasonable.
5:31:18
vtomole
As long as it's not split up too much. I think this stays true to SICL's goal of separating a CL implementation into modules. An implementer will clone the sub-components he/she wants.
5:31:31
beach
stylewarning: Since the basic specification (i.e. the Common Lisp HyperSpec) is stable, I don't think it will be a big problem.
5:33:28
beach
vtomole: It is still non-trivial to use those modules though. For Eclector, either an implementation uses it as a second reader (it has to have a reader in order to read the Eclector source code) or the implementation must cross compile on a different implementation the way SICl does.
5:37:01
beach
Right. But you are right. Take Eclector again. It has functionality that extends the Common Lisp HyperSpec, and that functionality is essential for client code, in particular source tracking. And it is important not to break client code that uses it.
5:39:37
vtomole
beach: To me, Common Lisp implementations are overwhelming. How is the back-end of SICL going? Are you still planning on compiling to x86_64? How much resources (time) does it take to write a "good" optimizing compiler?
5:42:52
beach
vtomole: The back-end is almost done. I have a separate repository containing an assembler for x86-64.
5:44:25
beach
vtomole: Hard to say how long it takes. I am not working on it full time, so it is taking longer.
5:46:15
vtomole
For sure, a lot of implementors compile their languages to LLVM because they don't want to deal with writing optimizers. But you are not worried about performance being equal to SBCL are you?
5:48:29
beach
It doesn't know how to do things like type inference, path replication, escape analysis and other things that are crucial to Common Lisp performance.
12:18:37
Colleen
Unknown command. Possible matches: 8, set, say, mop, get, hello, grant, time, tell, roll,
12:19:25
Colleen
pjb: Unknown command. Possible matches: 8, tell, set, get, time, help, deny, say, mop, test url,
12:22:33
Colleen
runs: Unknown command. Possible matches: 8, weather, set, say, mop, get, notify, grant, block, award,