about summary refs log tree commit diff stats
path: root/041name.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1668 - there's a bug in CHECK_TRACE_DOESNT_CONTAINKartik K. Agaram2015-06-271-0/+3
| | | | For starters start making the test fail when building until layer 41.
* 1648Kartik K. Agaram2015-06-251-1/+2
|
* 1641Kartik K. Agaram2015-06-241-10/+14
| | | | | | Snapshot in switching editor-data.cursor to editor-data.before-cursor. But I have trouble coercing events to touch events, even though using the integer tag 2 for the conversion works.
* 1597 - port more helpers from arc versionKartik K. Agaram2015-06-191-1/+1
|
* 1585Kartik K. Agaram2015-06-171-6/+6
|
* 1566 - fake mouse clicks in scenariosKartik K. Agaram2015-06-151-0/+1
|
* 1542 - more hacky tweaks for the replKartik K. Agaram2015-06-061-1/+1
|
* 1474 - another warningKartik K. Agaram2015-05-261-1/+21
|
* 1436Kartik K. Agaram2015-05-231-3/+0
|
* 1434 - support all unicode spacesKartik K. Agaram2015-05-231-12/+2
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-1/+0
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-17/+17
|
* 1389Kartik K. Agaram2015-05-161-2/+2
|
* 1387Kartik K. Agaram2015-05-161-3/+3
|
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-19/+19
| | | | ..now that we support non-integers.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-4/+4
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-4/+4
| | | | | | | | | | | | | | | 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.
* 1324 - warn when mixing named and numeric locationsKartik K. Agaram2015-05-101-38/+95
|
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-8/+8
| | | | | | | | | 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-41/+41
| | | | | | | | | | | | | | | | | | | 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/+204
I've tried to update the Readme, but there are at least a couple of issues.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-02 21:52:20 +0000