| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 5 days | fix things up so it gets through cold-start | Irene Knapp | |
| then it crashes on warm-start because warm-start doesn't exist yet Force-Push: yes Change-Id: I9eba481b31d48f9d32c3790f296204c5c8d90938 | |||
| 5 days | now there's a concept of pushing and popping input sources | Irene Knapp | |
| Force-Push: yes Change-Id: Ib8e8f342b7fa3773071eca36accf060f6c20f3be | |||
| 8 days | implement all the core Forth stuff in Evocation-assembly | Irene Knapp | |
| also, add support for ;asm and stuff Force-Push: yes Change-Id: I904bc0c31e7e4c8b0abc7790f3af5d20c275f2a5 | |||
| 10 days | implement more stuff in interpret.e | Irene Knapp | |
| it depended on the execution-model stuff, for the "next" macro. in general, any word implemented in assembly will depend on that. so, the execution stuff is moved into its own file, leaving evoke.e with only the job of bringing everything together. that's a little disappointing because talking about the execution model seems like a good introduction to the whole topic, but perhaps the problem can be solved down the line with literate programming... Force-Push: yes Change-Id: Ic2fe22dcc39980ef75763ae293e41024abc8ba38 | |||