about summary refs log tree commit diff stats
path: root/060string.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2095Kartik K. Agaram2015-08-281-9/+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.
* 2071Kartik K. Agaram2015-08-241-5/+5
|
* 2039 - warn on unbalanced '['Kartik K. Agaram2015-08-191-0/+72
|
* 2009Kartik K. Agaram2015-08-151-2/+2
|
* 1990 - extra ingredient for 'trace' depthKartik K. Agaram2015-08-131-2/+2
| | | | Now we can make use of all the depths from 1 to 99.
* 1926Kartik K. Agaram2015-08-031-1/+1
| | | | | | | 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-374/+361
|
* 1869 - rename the /deref property to /lookupKartik K. Agaram2015-07-281-127/+127
| | | | Should be a little bit more mnemonic.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-176/+176
| | | | First step to reducing typing burden. Next step: inferring types.
* 1808 - helper to print newlines during debuggingKartik K. Agaram2015-07-171-28/+7
| | | | | | | 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.
* 1780 - now we always reclaim local scopesKartik K. Agaram2015-07-131-21/+21
| | | | | | 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-21/+21
| | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part.
* 1697 - edit: starting to run codeKartik K. Agaram2015-07-031-1/+8
|
* 1599Kartik K. Agaram2015-06-191-4/+4
|
* 1597 - port more helpers from arc versionKartik K. Agaram2015-06-191-0/+560
|
* 1533 - repl: long-standing bug with backspaceKartik K. Agaram2015-06-061-1/+18
|
* 1520 - repl kinda workingKartik K. Agaram2015-06-021-5/+5
| | | | | But we really should test the top-level integration with 'run-interactive'.
* 1518 - still horribly brokenKartik K. Agaram2015-06-011-1/+10
| | | | | | Just figured out why a first keystroke of backspace was sending me out for a spin: run_interactive needs all early exits that don't actually run anything to increment the current_step_index(). FML, this is lousy..
* 1485 - start of a repl toolKartik K. Agaram2015-05-271-0/+28
| | | | | | | | | | | Doesn't actually work interactively yet; for some reason it prints in color, enter doesn't work, etc. It'll be interesting to try to add color and history as separate 'layers' using before/after. I'll also likely have to delete traces for its tests at some point as they inevitably explode in size.
* 1435Kartik K. Agaram2015-05-231-3/+7
|
* 1434 - support all unicode spacesKartik K. Agaram2015-05-231-2/+77
|
* 1433 - 'trim' stringsKartik K. Agaram2015-05-231-0/+96
|
* 1383 - warn on unknown typeKartik K. Agaram2015-05-161-1/+2
| | | | | | | | | | | | | This bit me in the last commit for the first time. Layer 010vm.cc is starting to look weird. It has references to stuff that gets implemented much later, like containers and exclusive containers. Its helpers are getting an increasing amount of logic. And it has no tests. I'm still inclined to think it's useful to have major data structures in one place, even if they aren't used for a bit. But those helpers should perhaps move out somehow or get some tests in the same layer.
* 1369Kartik K. Agaram2015-05-141-1/+1
| | | | | Delete comment-out marker from inside mu strings. Have to do this manually for now.
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-95/+95
| | | | ..now that we support non-integers.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-16/+0
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-0/+16
| | | | | | | | | | | | | | | 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.
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-22/+10
| | | | | | | | | | | | | | | | | | | 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
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+506
I've tried to update the Readme, but there are at least a couple of issues.