about summary refs log tree commit diff stats
path: root/029tools.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2095Kartik K. Agaram2015-08-281-1/+0
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 2079Kartik K. Agaram2015-08-261-20/+0
| | | | Cleanup 2078.
* 2078 - update entire screen on tb_present()Kartik K. Agaram2015-08-261-0/+20
| | | | | | | | | | | | | | | | | | | Termbox had been taking shortcuts when it thinks the screen hasn't changed, which doesn't work if some other process messes up the screen. The Go version has a Sync method in addition to Flush/tb_present for precisely this eventuality. But it feels like an unnecessary optimization given C's general speed. Just drop it altogether. --- This took me a long time to track down, and interestingly I found myself writing a new tracing primitive before I remembered how to selectively trace just certain layers during manual tests. I'm scared of generating traces not because of performance but because of the visual noise. Be aware of this. I'm going to clean up $log now. Maybe I should also stop using $print..
* 2064Kartik K. Agaram2015-08-241-3/+3
| | | | Adjust spaces in 'stash'.
* 1990 - extra ingredient for 'trace' depthKartik K. Agaram2015-08-131-8/+18
| | | | Now we can make use of all the depths from 1 to 99.
* 1989 - drop the default label for 'trace'Kartik K. Agaram2015-08-131-21/+8
|
* 1975 - let's start using traces in lessonsKartik K. Agaram2015-08-101-0/+47
| | | | | More friendly way to 'stash' stuff in the trace so that you can toggle lines of code to see their stashed traces.
* 1974Kartik K. Agaram2015-08-101-0/+6
|
* 1923Kartik K. Agaram2015-08-021-1/+1
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1922Kartik K. Agaram2015-08-021-1/+1
|
* 1921 - show trace by clicking on codeKartik K. Agaram2015-08-021-8/+15
| | | | | | | Region to click on to edit is now reduced to just the menu bar for the sandbox (excluding the 'x' for deleting the sandbox). The symmetry there might be useful, but we'll see if the relative click area is in line with how commonly the actions are performed.
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-1/+1
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1871Kartik K. Agaram2015-07-281-3/+0
|
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-1/+1
| | | | First step to reducing typing burden. Next step: inferring types.
* 1867 - keep tests from corrupting lesson/ directoryKartik K. Agaram2015-07-281-1/+4
|
* 1864Kartik K. Agaram2015-07-281-11/+0
|
* 1860 - new primitive: $systemKartik K. Agaram2015-07-271-0/+216
Also reorganize my miscellaneous hacky primitives.