libera/#clasp - IRC Chatlog
Search
21:19:14
yitzi
Well, at least poking around in lispStreams.cc has illuminated some issues I had with stream columns in Inravina. Looks like there are a few missing Gray stream methods like STREAM-LINE-COLUMN ((stream ansi-stream)....)
21:22:11
yitzi
Also, it seems like ANSI-STREAM is mostly useful to create Gray methods for the low level streams and avoid specializing on STREAM. So, I'm am going to go back to my original idea and move as much stuff from Stream_O into AnsiStream_O as possible.
1:28:05
Bike
should be fixed as of https://github.com/clasp-developers/clasp/commit/0c62ddec338f977a4d0b19cf33f32f429e1fc380
1:33:17
Bike
there's a bit of a deeper bug in slime that makes the error pop up instead of just going to an empty buffer, but it shouldn't go to an empty buffer to begin with
1:39:17
Bike
and i'm assuming where you see it is where i usually see it, which is i C-c C-c something and then try to M-. or go to frame source in sldb
2:52:19
Bike
so for the fasl format and native code, i think i may have to work with the JIT a little more directly
2:52:46
Bike
if i understand the faso code, what basically happens is that we load in an object file as a blob of bytes, and then we ask the jit for a special startup function that's in the object file, and then call that
2:53:49
Bike
but what i'd like is if we could load an object file, and then we just make a bunch of Function_O objects from the code in there, and maybe call them/etc normally later.
2:55:39
Bike
which is how it works with the bytecode. we load in the bytecode module, and then make a bunch of different bytecode functions with different entry points into the module.