about summary refs log tree commit diff stats
path: root/071print.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2014 - stop redundant prints on left-clickKartik K. Agaram2015-08-151-1/+1
|
* 1990 - extra ingredient for 'trace' depthKartik K. Agaram2015-08-131-1/+1
| | | | Now we can make use of all the depths from 1 to 99.
* 1969 - always hide screen before renderingKartik K. Agaram2015-08-101-0/+2
| | | | | | | | | | Also ensure we don't render unnecessarily. This is really where I want a formal type-like system to help me. All functions have paired calls to hide-screen and show-screen, except for the one in main. Only functions at the 'topmost' level are expected to hide/show.
* 1926Kartik K. Agaram2015-08-031-8/+4
| | | | | | | http://250bpm.com/blog:57 Funnily, the new idea I finally came up with in 'read' was already mirrored above in recipe 'write'.
* 1883 - type-deducing in more .mu filesKartik K. Agaram2015-07-291-230/+224
|
* 1881Kartik K. Agaram2015-07-291-102/+102
|
* 1869 - rename the /deref property to /lookupKartik K. Agaram2015-07-281-114/+114
| | | | Should be a little bit more mnemonic.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-83/+83
| | | | First step to reducing typing burden. Next step: inferring types.
* 1808 - helper to print newlines during debuggingKartik K. Agaram2015-07-171-12/+6
| | | | | | | 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.
* 1803Kartik K. Agaram2015-07-171-8/+9
| | | | | Bring back my optimizations for avoiding unnecessary work. But they shouldn't be needed for correctness, and they aren't.
* 1802 - cleanupKartik K. Agaram2015-07-171-54/+0
|
* 1800 - ah, found the bounds-checking bugKartik K. Agaram2015-07-171-32/+30
| | | | I was counting locations when I should have been counting elements.
* 1799 - continue to debug memory corruption of 1795Kartik K. Agaram2015-07-171-10/+95
| | | | | | | | | | | | 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-43/+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/+43
| | | | I'm writing to location 'screen' somehow that's not the raw location.
* 1780 - now we always reclaim local scopesKartik K. Agaram2015-07-131-20/+20
| | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring.
* 1773 - update all mu recipes to new-default-spaceKartik K. Agaram2015-07-131-20/+20
| | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part.
* 1750Kartik K. Agaram2015-07-101-0/+1
| | | | | No, that's a false alarm. There's just a larger screen to manipulate. But the size of the screen doesn't change in interactive mode.
* 1708Kartik K. Agaram2015-07-041-3/+3
| | | | | | Simpler gradient computation. But in the end it looks better when the gradient is so subtle as to be irrelevant. Might as well eliminate the gradient altogether.
* 1705 - change background colorKartik K. Agaram2015-07-041-3/+21
|
* 1671 - better separate setup from code under testKartik K. Agaram2015-06-271-0/+2
| | | | | Requires better support for special variable names in scenarios like 'screen' and 'console'.
* 1656 - smooth refresh doneKartik K. Agaram2015-06-251-0/+26
| | | | Had to take control of tb_present() after all. Termbox was wise.
* 1655 - first attempt at smooth refresh: hide-cursorKartik K. Agaram2015-06-251-0/+26
| | | | | But it doesn't work, because moving the cursor inside 'render' also starts displaying it again.
* 1599Kartik K. Agaram2015-06-191-11/+11
|
* 1571Kartik K. Agaram2015-06-161-2/+87
|
* 1569Kartik K. Agaram2015-06-161-3/+27
|
* 1545 - sketching out a simple editor widgetKartik K. Agaram2015-06-081-0/+28
|
* 1534 - print results in a different colorKartik K. Agaram2015-06-061-2/+14
|
* 1481Kartik K. Agaram2015-05-261-5/+5
|
* 1478Kartik K. Agaram2015-05-261-2/+2
|
* 1477Kartik K. Agaram2015-05-261-0/+15
|
* 1476 - fake screens support colorKartik K. Agaram2015-05-261-28/+58
|
* 1458Kartik K. Agaram2015-05-251-1/+1
| | | | | | | | | | | | | | | | While pushing out color support in fake screens I realized I've been complecting the special-case of a special-case to transform literal-string arguments for 'new'. As a result I hadn't been catching bad habits like giving its arg the wrong type. Now we have cleaner separation of the two variants of 'new', a few more checks, and better error messages when we mis-call it. Aside: I've added a third goto target. Sliding into spaghetti? Keep an eye on it. This goto might become a common pattern: a layer hooking into a previous one to prevent it from happening. In this case new on literal-strings prevents the transform for new from triggering.
* 1374 - chessboard end-to-end test passes!Kartik K. Agaram2015-05-141-0/+9
| | | | | | | | | | After like 40 seconds (because of the 120-column screen), but whatever. The final bug was that clear-screen wasn't actually working right for fake screens. (The trace is too large for github, so I'm going to leave it out for now.)
* 1369Kartik K. Agaram2015-05-141-4/+4
| | | | | Delete comment-out marker from inside mu strings. Have to do this manually for now.
* 1368 - alias carriage-return and newlineKartik K. Agaram2015-05-141-2/+2
| | | | | | | CRLF still shows as two newlines, though. Cross that bridge when we get to it. The new chessboard test is still hanging, though.
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-81/+81
| | | | ..now that we support non-integers.
* 1362Kartik K. Agaram2015-05-131-6/+6
| | | | | | | | Mu allows us to use multiple ingredients/products without commas, but make sure we don't. $ grep "<- [^ ]\+ [^#\[,]* [^#\[,]*$" * $ grep "^[ ]*[^ #,][^#,]* [^#,]* <- " *
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-1/+1
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-1/+1
| | | | | | | | | | | | | | | I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily *persuade others* that I've gotten it right.
* 1323 - keyboard supports backspace and newlineKartik K. Agaram2015-05-101-12/+78
| | | | | | Lots mixed into this commit: some off-by-one errors in display.cc a new transform to translate jump labels that I'd somehow never gotten around to supporting
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-19/+5
| | | | | | | | | | | | | | | | | | | All primitives now always write to all their products. If a product is not used that's fine, but if an instruction seems to expect too many products mu will complain. In the process, many primitives can operate on more than two ingredients where it seems intuitive. You can add or divide more than two numbers together, copy or negate multiple corresponding locations, etc. There's one remaining bit of ugliness. Some instructions like get/get-address, index/index-address, wait-for-location, these can unnecessarily load values from memory when they don't need to. Useful vim commands: %s/ingredients\[\([^\]]*\)\]/ingredients.at(\1)/gc %s/products\[\([^\]]*\)\]/products.at(\1)/gc .,$s/\[\(.\)]/.at(\1)/gc
* 1293 - start porting the chessboard app overKartik K. Agaram2015-05-061-6/+70
| | | | | | | | | Just to put all our new test primitives through their paces, and iron out any kinks. Just the one chessboard scenario is taking 1.5-2.5x all the tests we've written so far. But we're starting from a faster baseline, that was the point of the C++ port. I also have -O3 optimizations in my back-pocket.
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+274
I've tried to update the Readme, but there are at least a couple of issues.