Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 1803 | Kartik K. Agaram | 2015-07-17 | 2 | -10/+11 |
| | | | | | Bring back my optimizations for avoiding unnecessary work. But they shouldn't be needed for correctness, and they aren't. | ||||
* | 1802 - cleanup | Kartik K. Agaram | 2015-07-17 | 4 | -92/+49 |
| | |||||
* | 1801 - assertion failures fixed | Kartik K. Agaram | 2015-07-17 | 1 | -12/+11 |
| | | | | | | Now we can investigate the remaining issues: print-string to main screen not working to print 'screen:' print-integer to toy screen not working to print '4' | ||||
* | 1800 - ah, found the bounds-checking bug | Kartik K. Agaram | 2015-07-17 | 4 | -55/+168 |
| | | | | I was counting locations when I should have been counting elements. | ||||
* | 1799 - continue to debug memory corruption of 1795 | Kartik K. Agaram | 2015-07-17 | 7 | -240/+329 |
| | | | | | | | | | | | | 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. | ||||
* | 1798 - support for deleting sandboxes | Kartik K. Agaram | 2015-07-16 | 1 | -1/+144 |
| | |||||
* | 1797 - widget to delete sandbox | Kartik K. Agaram | 2015-07-16 | 1 | -7/+24 |
| | | | | Doesn't work yet. | ||||
* | 1796 - temporarily undo 1795 | Kartik K. Agaram | 2015-07-16 | 5 | -244/+24 |
| | | | | | Debugging simulated-screen support is taking too long, and I suddenly have a few higher priorities. | ||||
* | 1795 - still debugging screen-in-screen rendering | Kartik K. Agaram | 2015-07-16 | 5 | -24/+244 |
| | | | | I'm writing to location 'screen' somehow that's not the raw location. | ||||
* | 1794 - stop redundantly recompiling on .mu changes | Kartik K. Agaram | 2015-07-16 | 1 | -2/+6 |
| | |||||
* | 1793 - rudimentary sandboxing for scenarios in the environment | Kartik K. Agaram | 2015-07-15 | 2 | -2/+11 |
| | |||||
* | 1792 - better semantics for ctrl-k | Kartik K. Agaram | 2015-07-15 | 1 | -3/+122 |
| | | | | More evidence that the choice of 'before-cursor' was inspired. | ||||
* | 1791 - delete to start/end of line | Kartik K. Agaram | 2015-07-15 | 1 | -0/+166 |
| | |||||
* | 1790 - move to end of line | Kartik K. Agaram | 2015-07-15 | 1 | -0/+145 |
| | |||||
* | 1789 - move to start of line with home/ctrl-a | Kartik K. Agaram | 2015-07-15 | 1 | -2/+133 |
| | |||||
* | 1788 | Kartik K. Agaram | 2015-07-15 | 1 | -1/+3 |
| | |||||
* | 1787 - clear warnings between runs | Kartik K. Agaram | 2015-07-15 | 2 | -29/+39 |
| | |||||
* | 1786 - render only the side that changed | Kartik K. Agaram | 2015-07-15 | 1 | -8/+33 |
| | |||||
* | 1785 | Kartik K. Agaram | 2015-07-15 | 1 | -5/+23 |
| | |||||
* | 1784 - start making render more efficient | Kartik K. Agaram | 2015-07-15 | 1 | -1/+0 |
| | | | | | We stopped rendering just the widget under focus when we switched away from the simplistic list of editors. Need to bring that back. | ||||
* | 1783 - stable if sluggish on caleb's 512MB server | Kartik K. Agaram | 2015-07-14 | 2 | -8/+45 |
| | | | | | Profiling shows the bulk of time is spent in read_memory, canonize, absolutize. But I'm not sure how to optimize those places. | ||||
* | 1782 - stop tracing anything but warnings inside edit | Kartik K. Agaram | 2015-07-14 | 3 | -4/+7 |
| | | | | | | | | | Speeds up edit.mu tests by 10x, and shrinks memory usage by 100x. We need a more efficient implementation of traces, but we can keep going for now. We didn't really need to reclaim memory just yet, after all. Mu is pretty memory-efficient. | ||||
* | 1781 - the hog is Trace_stream, not Memory | Kartik K. Agaram | 2015-07-14 | 2 | -0/+19 |
| | | | | | 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 scopes | Kartik K. Agaram | 2015-07-13 | 17 | -123/+168 |
| | | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring. | ||||
* | 1779 | Kartik K. Agaram | 2015-07-13 | 1 | -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. | ||||
* | 1778 | Kartik K. Agaram | 2015-07-13 | 36 | -166/+361 |
| | |||||
* | 1777 - consistent terminology: 'product' | Kartik K. Agaram | 2015-07-13 | 4 | -9/+9 |
| | |||||
* | 1776 | Kartik K. Agaram | 2015-07-13 | 1 | -0/+0 |
| | |||||
* | 1775 | Kartik K. Agaram | 2015-07-13 | 3 | -2/+2 |
| | |||||
* | 1774 | Kartik K. Agaram | 2015-07-13 | 3 | -4/+4 |
| | |||||
* | 1773 - update all mu recipes to new-default-space | Kartik K. Agaram | 2015-07-13 | 14 | -113/+113 |
| | | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part. | ||||
* | 1772 - stop wasting space when allocating default-space | Kartik K. Agaram | 2015-07-13 | 1 | -0/+47 |
| | | | | Let's see how much this helps edit.mu. | ||||
* | 1771 | Kartik K. Agaram | 2015-07-13 | 2 | -1/+16 |
| | |||||
* | 1770 - globals now work with names | Kartik K. Agaram | 2015-07-13 | 1 | -2/+23 |
| | | | | We won't bother supporting names for globals, for now. | ||||
* | 1769 - routines can now have global variables | Kartik K. Agaram | 2015-07-13 | 3 | -12/+54 |
| | |||||
* | 1768 | Kartik K. Agaram | 2015-07-13 | 7 | -0/+0 |
| | |||||
* | 1767 | Kartik K. Agaram | 2015-07-13 | 3 | -0/+0 |
| | |||||
* | 1766 | Kartik K. Agaram | 2015-07-12 | 45 | -2001/+1851 |
| | |||||
* | 1765 | Kartik K. Agaram | 2015-07-11 | 1 | -18/+52 |
| | | | | | As usual, trying to fix this manually was a false economy. Writing this test in the first place would have made debugging much simpler. | ||||
* | 1764 - editor now updates all sandboxes | Kartik K. Agaram | 2015-07-11 | 3 | -15/+61 |
| | | | | Finally, albeit too late for my demo. | ||||
* | 1763 - warn on break/loop outside {} | Kartik K. Agaram | 2015-07-11 | 1 | -85/+54 |
| | |||||
* | 1762 - numbers without types = literals | Kartik K. Agaram | 2015-07-11 | 1 | -0/+4 |
| | | | | Quick hack for demo at balisp meetup today. | ||||
* | 1761 - multiple sandboxes seems to be working | Kartik K. Agaram | 2015-07-11 | 1 | -1/+0 |
| | | | | No idea why this was wrong, but whatever.. | ||||
* | 1760 - failing test for multiple sandboxes | Kartik K. Agaram | 2015-07-11 | 1 | -53/+76 |
| | | | | | | | | | We're starting to hit the limits of my 8GB RAM, to the point where I'm starting to economize on the size of the screen. Time to start thinking about reclaiming memory. Anyways, test now fails in the right place. I'm failing to propertly render intermediate lines between sandboxes. | ||||
* | 1759 | Kartik K. Agaram | 2015-07-11 | 2 | -2/+6 |
| | |||||
* | 1758 - now clear sandbox editor on F10 | Kartik K. Agaram | 2015-07-11 | 1 | -13/+47 |
| | | | | We're ready to start displaying multiple sandboxes. | ||||
* | 1757 | Kartik K. Agaram | 2015-07-11 | 1 | -7/+12 |
| | |||||
* | 1756 | Kartik K. Agaram | 2015-07-11 | 1 | -7/+19 |
| | |||||
* | 1755 | Kartik K. Agaram | 2015-07-10 | 1 | -13/+13 |
| | |||||
* | 1754 | Kartik K. Agaram | 2015-07-10 | 3 | -16/+19 |
| |