Alex Shinn
Alex Shinn
There's `sexp_opcode_data` (and data2) which is accessible from the `self` binding from the stub: ``` sexp sexp_foo (sexp ctx, sexp self, sexp_sint_t n) { ... res = foo(self == NULL...
Logging uses custom date formatting written in Scheme and writes all mime headers as an sexp (using the expensive and generalized `write`). For now added a --quiet option to disable...
Probably easiest to statically include SRFI 69 in the Plan9 build.
Sorry about that, this was refactored and improved by Chris Walsh in 2005c19ea. You want to use `sexp dst = sexp_gc_heap_pack(ctx, new_size_or_zero)`.
1. Yes, it would be possible, but 1. I'm not sure how much faster it would be, and 2. it's tricky code that I don't have time to maintain. 2....
I can't reproduce this - I consistently get an error calling set-car! on a literal: ``` > (define mypair '(1 . 2)) > mypair (1 . 2) > (set-car! mypair...
This is the SRFI 38 implementation. It's a little tedious to fix, in part because it's fully portable, and in part because it actually needs to use `set-c*r!` to support...
Sure, we could add that. Since it has to duplicate the shared structure detection of SRFI 38 it would be more work, but at the same time be generally useful.
I'm not sure I follow. Are you suggesting a circular dependency? This doesn't really apply since the repl itself is not part of the standard. The SRFI 38 `read/ss` is...
Chibi is intentionally built in layers. The C reader/writer is fast and simple and handles all standard syntax but only reads, not writes, shared structures. The Scheme reader is actually...