implement more stuff in interpret.e

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

0 files changed, 0 insertions, 0 deletions