about summary refs log tree commit diff stats
path: root/043new.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1849Kartik K. Agaram2015-07-251-1/+1
|
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-14/+20
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-15/+18
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.
* 1832Kartik K. Agaram2015-07-241-1/+1
|
* 1822Kartik K. Agaram2015-07-191-2/+2
|
* 1799 - continue to debug memory corruption of 1795Kartik K. Agaram2015-07-171-1/+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.
* 1781 - the hog is Trace_stream, not MemoryKartik K. Agaram2015-07-141-0/+18
| | | | | I keep forgetting about it. Until, that is, I run gprof. Even if I think I need a memory profile, a cpu profile is a pretty good proxy.
* 1780 - now we always reclaim local scopesKartik K. Agaram2015-07-131-1/+1
| | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring.
* 1779Kartik K. Agaram2015-07-131-0/+86
| | | | | | Now we can reclaim allocated space. But the API's suspect. I still want to provide some sort of tree of allocations. For now we'll use this only to reclaim default-spaces. That's next.
* 1768Kartik K. Agaram2015-07-131-0/+257