about summary refs log tree commit diff stats
path: root/036call_reply.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1799 - continue to debug memory corruption of 1795Kartik K. Agaram2015-07-171-0/+1
| | | | | | | | | | | | Things I figured out: - 'row' in render-screen doesn't perfectly track cursor-row in screen - proximal cause was forgetting to add left:number to stop-printing - trying to print to screen outside bounds was silently succeeding and corrupting simulated memory - if we silently ignore prints outside bounds things are fine But why are prints outside screen bounds working? We should be accessing screen data using 'index', and that's checking its bounds.
* 1796 - temporarily undo 1795Kartik K. Agaram2015-07-161-1/+0
| | | | | Debugging simulated-screen support is taking too long, and I suddenly have a few higher priorities.
* 1795 - still debugging screen-in-screen renderingKartik K. Agaram2015-07-161-0/+1
| | | | I'm writing to location 'screen' somehow that's not the raw location.
* 1777 - consistent terminology: 'product'Kartik K. Agaram2015-07-131-2/+2
|
* 1754Kartik K. Agaram2015-07-101-0/+2
|
* 1745 - hoist warning/response strings out of editor-dataKartik K. Agaram2015-07-101-1/+17
| | | | | | | | | | Still ugly as hell. Some tests failing, but they're most likely wrong. We need to test cursor positioning at the level of the environment and take it away from the responsibilities of individual editors. Also bring back the line at the bottom of each editor. The non-test run ('main' in edit.mu) is completely borked. Sluggish as hell, and I can't seem to switch focus to the sandbox editor.
* 1723Kartik K. Agaram2015-07-081-4/+1
| | | | | Some reorg before we start plumbing 'reply' from 'run-interactive' to return a string containing the results.
* 1721 - hide warnings inside interactive routinesKartik K. Agaram2015-07-081-2/+4
| | | | | | | | | | We will need many other forms of isolation for these. For starters we're going to have to replace most asserts with warnings that can be traced so that the environment doesn't crash because of illegal code typed into it. New test is still failing. Just getting it to fail right was hard enough.
* 1716Kartik K. Agaram2015-07-071-0/+2
|
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-5/+5
| | | | | | | It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
* 1698Kartik K. Agaram2015-07-031-0/+158