diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-02-20 22:14:06 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-02-20 22:14:09 -0800 |
commit | 4a37291e2d68cb4c9a49dfb816882b963a1cfe90 (patch) | |
tree | def5aa0f5a7060b548f9f2cbcd1635cc10b7f283 /304screen.subx | |
parent | bcb2190ec370b2009fd3ff6faf690758e4cd8e69 (diff) | |
download | mu-4a37291e2d68cb4c9a49dfb816882b963a1cfe90.tar.gz |
7759 - changing course; delete the postfix shell
It might be too ambitious for an initial Mu system, and I also want to watch my novelty budget. I also have great doubts about the ability of this live-updating postfix system to scale to interesting programs. Conditionals, loops, multi-line functions, all this requires further work. Instead, I'm going to recenter around Mu's original goals: - saying no to most features - encouraging/teaching testing - traces as a unifying metaphor In particular, instead of a live-updating system, the new debug loop will be: - generate a trace - browse the trace - modify the program - generate a trace - ... The only persistence we'll need here is a way to track what the programmer has drilled into in the trace. That might have some commonalities with the old system of expanded words.
Diffstat (limited to '304screen.subx')
0 files changed, 0 insertions, 0 deletions