freenode/#lisp - IRC Chatlog
Search
7:20:34
beach
Let me say this again: If y'all are bored, I can give you some SICL-related tasks to accomplish.
7:41:55
contrapunctus
I'd try, but I know neither compilers nor as much CL as I'd like. Instead, I'm trying to design a set of malleable programs, exploring at least CL (+ CLIM) and Smalltalk as solutions.
9:22:19
beach
Actually, I do have a task for someone who would be interested in contributing to the SICL project. The FORMAT module is one of the first modules I wrote, and it is not particularly coupled to the rest of SICL, so it could be extracted to a separate repository. There are a few directives missing, so those are additional tasks to work on.
9:22:20
beach
And the directive interpreter exists, but the directive compiler should be written at some point. The current (huge) file format.lisp should be split up into several smaller files, probably with the code for one directive in each file. And a test suite is needed, probably mostly taken from the ANSI test suite I would imagine.
9:23:59
beach
Two systems should be supplied, one for "intrinsic" use, i.e. in a system that does not already have FORMAT, and one for "extrinsic" use, i.e. for testing in a system that has FORMAT that we don't want to clobber. Each system should have an appropriate package definition.
9:24:59
beach
It would be possible for a relative newbie to take on this task, in which case, guidance will be provided.
12:38:43
phoe
;; debugger invoked on a SB-INT:SIMPLE-READER-ERROR: no dispatch function defined for #\/
12:51:25
lisp373
Hey guys, is there a way to undefine a method? I get the "attempt to add the method ... but the method and generic function differ in whether they accept" error
13:02:04
phoe
oh, right, (defgeneric foo ()) (defmethod foo (&key x)) is going to error on DEFMETHOD
13:02:38
beach
Right, but what if the generic function is reinitialized with a different argument list.
13:54:10
puchacz
I am happy with slime, but as usual - maybe I am missing something I don't even know about
13:55:47
contrapunctus
New to CL...not a fan of how the number for ABORT* changes in different situations. I'd rather have numbers for common restarts in the beginning 🤔
13:56:16
phoe
contrapunctus: multiple ABORT restarts may mean different things, that's why there's multiple
13:57:23
phoe
beach: I know you're jaded, but that comment actually brings nothing to the discussion
13:58:44
contrapunctus
I mentioned CL21, so some CL users said that the changes they want can't be made as libraries. So I suggested making a revised community standard.
13:59:27
phoe
1) someone needs to actually go and do that, and these people are either gonna be volunteers or someone finds a funding source
13:59:40
phoe
2) someone needs to actually go and have implementers adopt it, and these people are either gonna be volunteers or someone finds a funding source
14:00:13
beach
phoe: You forget that those people have to be competent in language design and compiler design.
14:02:31
phoe
but then again, we're talking about a new one whereas the old one is still heavily unmaintained and there's no good user-facing CL documentation that isn't a book or the good ol' CLHS that is not meant to be user-facing documentation
14:03:30
phoe
once we have that, we can create a separate version that is not *the* specification but is actually useful because it contains better examples and bugfixes and what not, and then implement WSCL on top of that