freenode/#clasp - IRC Chatlog
Search
3:10:37
beach
I thought you had abandoned trying to implement first-class global environments in Clasp, given that it is not very costly to just start a process for each user.
3:11:51
Bike
for one, even if i did that, it would still have unrestricted access to the filesystem and such
3:14:11
beach
I am pleased that you are working on it, because I think you will figure out lots of issues that would otherwise pop up later on in my SICL development.
3:15:16
Bike
CLOS is going to be annoying though, i can understand a little more now why you go through like four environments
3:18:42
beach
Yeah, CLOS is complicated that way. Recently, I have considered converting some of the generic functions to ordinary functions to avoid some of the problems with simultaneous but different mappings from names to objects.
3:19:42
beach
I have nothing concrete yet, but when I start contemplating SICL bootstrapping again, I will keep that option in mind if I get into trouble.
3:24:36
beach
Yeah, that's not the problem I had in mind. It is possible that, in the same bootstrapping phase, I need two different definitions of some function, called by two different generic functions. I might be able to fix that problem by inlining two different versions of the function and converting at least one of the generic functions to an ordinary function.
3:31:24
beach
The problem is that, in each bootstrapping phase, I use some classes created by the previous phase, and those are often "the same" classes, i.e. the MOP hierarchy of classes, but represented differently in each phase. In phase 1, they are ordinary host classes. In phase 2, they are host non-class instances. In phase 3, they are host header/rack combinations. I often need to call different versions of things like allocate-instance or
12:59:29
Shinmera
I've hard reports about Portacle breaking on it (again) but I haven't tested it myself
13:00:20
Shinmera
Makes you really appreciate the "never break userland" attitude Linus has for the kernel.