about summary refs log tree commit diff stats
path: root/021arithmetic.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2178 - don't die on divide by 0Kartik K. Agaram2015-09-101-6/+25
|
* 2095Kartik K. Agaram2015-08-281-1/+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.
* 1953 - more warningsKartik K. Agaram2015-08-071-7/+29
|
* 1923Kartik K. Agaram2015-08-021-2/+2
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-3/+3
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-20/+20
| | | | First step to reducing typing burden. Next step: inferring types.
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-0/+12
| | | | Also standardized warnings.
* 1764 - editor now updates all sandboxesKartik K. Agaram2015-07-111-0/+1
| | | | Finally, albeit too late for my demo.
* 1726Kartik K. Agaram2015-07-081-2/+2
|
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-5/+5
| | | | | | | It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-52/+0
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-10/+18
|
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-25/+28
| | | | ..now that we support non-integers.
* 1360 - store doubles in memoryKartik K. Agaram2015-05-121-5/+12
| | | | | | | | | | | | | This is a far cleaner way to provide *some* floating-point support. We can only represent signed integers up to 2^51 rather than 2^63. But in exchange we don't have to worry about it elsewhere, and it's probably faster than checking tag bits in every operation. Hmm, yeah, surprised how easy this was. I think I'll give up on the other approach. I still don't have non-integer literals. But we won't bother with those until we need them. `3.14159:literal` seems ugly.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-218/+16
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-82/+145
| | | | | | | | | | | | | | | 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.
* 1349 - snapshot: floating-point supportKartik K. Agaram2015-05-111-0/+139
|
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-68/+71
| | | | | | | | | | | | | | | | | | | 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/+226
I've tried to update the Readme, but there are at least a couple of issues.