freenode/#sicl - IRC Chatlog
Search
7:46:32
beach
The boot procedure finishes successfully with the explicit argument-processing code!!!!
8:00:43
beach
Now, I can again think about HIR-to-MIR. For the initial executable, I initially thought I would simplify the argument-passing convention, but with this explicit argument-processing code, I don't think I have to do that. The only slight complication in MIR, or even later in LIR, is that I may have to insert a loop that moves all the arguments on the stack in order to make room for the lexical variables. But that loop is pretty
8:02:23
beach
In fact, if I keep the convention final convention I planned, the instruction COMPUTE-ARGUMENT-COUNT is trivial, because the argument count is in one of the registers.
8:13:36
beach
heisig: And again, thank you for making me think harder about argument processing in HIR.
8:14:38
beach
I still need to document that code, since it is incomprehensible. I'll just refer to the specification which I think is fairly clear.
8:15:24
heisig
I'm working on trucler-native this morning. Which is also interesting because it forces me to examine the Trucler protocol very closely.
8:16:01
beach
Since you are at it, consider what stuff (code and documentation) should be moved to the reference implementation.
8:17:16
heisig
For example, when working on SBCL environments, I realized that the low-level augmentation functions are really only useful for trucler-reference.
8:18:34
heisig
Oh, and something I wanted to ask - the CLTL function AUGMENT-ENVIRONMENT can add any number of bindings and declarations simultaneously. Why did you decide against that?
8:22:20
beach
I decided against the entire CLtL2 protocol because it is not extensible and can not be customized, and that is because it does not use generic functions.