about summary refs log tree commit diff stats
path: root/030container.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-5/+5
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-18/+18
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.
* 1834Kartik K. Agaram2015-07-241-4/+8
|
* 1833Kartik K. Agaram2015-07-241-1/+8
|
* 1832Kartik K. Agaram2015-07-241-1/+4
|
* 1826 - edit: start carefully showing all errorsKartik K. Agaram2015-07-211-2/+4
| | | | | | | | | | | | | | | | | | | | | Eventually we might be able to get rid of die entirely. This is just a preliminary stab at a random error. In the process I ran into two issues that have impeded debugging before: a) Naming conflicts within scenarios are a real no-no. I need to warn on them, but the rules are getting complicated: Always print warnings on redefine But not in interactive mode Or in scenarios checking warning behavior Unless the scenario recipe itself is overridden b) Now that we've added collect_layers and a long time can go between traces, debugging is a minefield because trace lines don't print to screen immediately after they're created. Need to do something about that. Maybe explicitly trigger collection by tracing '\n' or something. These are the next two items on my todo list.
* 1800 - ah, found the bounds-checking bugKartik K. Agaram2015-07-171-5/+50
| | | | I was counting locations when I should have been counting elements.
* 1744 - support just two editors rather than a listKartik K. Agaram2015-07-091-0/+4
| | | | | Current model: you click on something to put it on the editor at the top of the column. Worth a shot.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-36/+36
| | | | | | | 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!
* 1668 - there's a bug in CHECK_TRACE_DOESNT_CONTAINKartik K. Agaram2015-06-271-0/+1
| | | | For starters start making the test fail when building until layer 41.
* 1629 - new helper for constructing containersKartik K. Agaram2015-06-231-0/+27
|
* 1604Kartik K. Agaram2015-06-201-1/+2
|
* 1593Kartik K. Agaram2015-06-181-1/+2
|
* 1586Kartik K. Agaram2015-06-171-1/+1
|
* 1585Kartik K. Agaram2015-06-171-2/+2
|
* 1497 - 2 boneheaded bugs in parsing scenariosKartik K. Agaram2015-05-281-0/+12
|
* 1474 - another warningKartik K. Agaram2015-05-261-7/+10
|
* 1417 - draft zoom levels in tracesKartik K. Agaram2015-05-211-3/+3
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-21/+0
|
* 1399 - better 'unknown type' warningsKartik K. Agaram2015-05-181-3/+94
| | | | | | | | Implement warnings for types without definitions without constraining where type definitions must appear. We also eliminate the anti-pattern where a change in layer 10 had its test in layer 11 (commit 1383).
* 1398Kartik K. Agaram2015-05-181-2/+23
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-16/+16
|
* 1390 - support non-integer literalsKartik K. Agaram2015-05-171-5/+0
| | | | | | | | | | | | | | | | | | | | Since '3.14159:literal' looks ugly, we'll just say '3.14159'. It's not like non-integers can be confused for anything but literals. Once I tried to turn reagent values into doubles, I uncovered a bug: arithmetic using signed integers is busted; if either operand of subtraction is unsigned the result is unsigned as well. If it needs to be negative: ka-boom. It was only masked because I was eventually storing the result in a long long int, where it was out of range, and so overflowing into the correct signed value. Once I switched to doubles the unsigned value would indeed fit without overflowing. Ka-boom. Yet another reminder that unsigned integers suck. I started using them mostly to avoid warnings in loops when comparing with .size(), which is usually a size_t. Who knows what other crap lurks here. Just use signed integers everywhere. (And avoid bitwise operators.)
* 1367Kartik K. Agaram2015-05-141-0/+87
|
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-41/+41
| | | | ..now that we support non-integers.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-6/+4
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-4/+6
| | | | | | | | | | | | | | | 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.
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-1/+1
| | | | | | | | | Useful check: $ grep "[^ '\"]\[[^\"]" *.cc \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |grep '[^ ]\['
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-30/+52
| | | | | | | | | | | | | | | | | | | 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/+169
I've tried to update the Readme, but there are at least a couple of issues.