Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 1391 - avoid unsigned integers | Kartik K. Agaram | 2015-05-17 | 1 | -2/+2 |
| | |||||
* | 1330 | Kartik K. Agaram | 2015-05-10 | 1 | -1/+0 |
| | |||||
* | 1327 - better error handling in chessboard | Kartik K. Agaram | 2015-05-10 | 1 | -2/+1 |
| | | | | | Also a bugfix in break to label, because I noticed the screen wasn't being cleaned up on quit. | ||||
* | 1323 - keyboard supports backspace and newline | Kartik K. Agaram | 2015-05-10 | 1 | -1/+3 |
| | | | | | | 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 | ||||
* | 1303 | Kartik K. Agaram | 2015-05-07 | 1 | -1/+1 |
| | |||||
* | 1298 - better ingredient/product handling | Kartik K. Agaram | 2015-05-07 | 1 | -5/+6 |
| | | | | | | | | | | | | | | | | | | | 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 | ||||
* | 1296 - roll back 1295 | Kartik K. Agaram | 2015-05-07 | 1 | -1/+0 |
| | |||||
* | 1295 - broken snapshot | Kartik K. Agaram | 2015-05-07 | 1 | -0/+1 |
| | | | | | I spent a couple of hours debugging this because routine-state only sometimes writes to its product. This is unacceptable. Fix this first. | ||||
* | 1276 - make C++ version the default | Kartik K. Agaram | 2015-05-05 | 1 | -0/+20 |
I've tried to update the Readme, but there are at least a couple of issues. |