| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 1808 - helper to print newlines during debugging | Kartik K. Agaram | 2015-07-17 | 1 | -1/+4 |
| | | | | | | | | The recent session makes me weary of deleting comment counts from inside strings, and the newlines everywhere take up vertical space. Considered println like pascal/ruby, but I'd like something I can add/remove at the end of existing prints. So this hack for $print. | ||||
| * | 1802 - cleanup | Kartik K. Agaram | 2015-07-17 | 1 | -0/+1 |
| | | |||||
| * | 1799 - continue to debug memory corruption of 1795 | Kartik K. Agaram | 2015-07-17 | 1 | -0/+29 |
| | | | | | | | | | | | | | 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. | ||||
| * | 1767 | Kartik K. Agaram | 2015-07-13 | 1 | -0/+105 |