Duy Nguyen
Duy Nguyen
fyi srfi-159 (scheme show) also has this `fl`
might be related to #532
On master, it seems to work ``` gosh[r7rs.user]$ (foo bar) #:record-set-name!.617 ```
> when an error automatically triggers the debugger. 99 out of 100 cases I don't need to inspect the error frame... I'd say 8 or 9 out of 10 times....
> But actually, debugger doesn't need to be associated with error; we can enter debugger from a breakpoint, or one thread can stop another thread (there's already such a feature)...
From the original issue > imho we shouldn't optimize for this. Just add a commodity to amounts. It really isn't that hard and makes things explicit. It is hard. I...
Oh I thought of that. The think is the numbers at the end of the payer line, or are followed by comments... so it's not exactly straightforward. And I also...
Scripting isn't a problem, I could do it. My problem is verification because there are _a lot_ of transactions to check (visually). It just occurs to me though that if...
Even generating gauche--uvector.c still takes a lot of time (20s or something) to generate 7.2MB, so yeah splitting sounds great.
To be pedantic, it's both a compiler and an interpreter. And it should run on other 32-bit platforms as well, at least ARM.