about summary refs log tree commit diff stats
path: root/072scenario_screen.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-14/+14
| | | | | | | At the lowest level I'm reluctantly starting to see the need for errors that stop the program in its tracks. Only way to avoid memory corruption and security issues. But beyond that core I still want to be as lenient as possible at higher levels of abstraction.
* 2232Kartik K. Agaram2015-10-011-0/+12
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-8/+10
| | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well?
* 2199 - stop printing numbers in scientific notationKartik K. Agaram2015-09-141-5/+5
| | | | | | | | | | | Turns out the default format for printing floating point numbers is neither 'scientific' nor 'fixed' even though those are the only two options offered. Reading the C++ standard I found out that the default (modulo locale changes) is basically the same as the printf "%g" format. And "%g" is basically the shorter of: a) %f with trailing zeros trimmed b) %e So we'll just do %f and trim trailing zeros.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-15/+15
| | | | First step to reducing typing burden. Next step: inferring types.
* 1849Kartik K. Agaram2015-07-251-23/+1
|
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-5/+5
| | | | | | | | | 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.
* 1721 - hide warnings inside interactive routinesKartik K. Agaram2015-07-081-5/+15
| | | | | | | | | | We will need many other forms of isolation for these. For starters we're going to have to replace most asserts with warnings that can be traced so that the environment doesn't crash because of illegal code typed into it. New test is still failing. Just getting it to fail right was hard enough.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-11/+11
| | | | | | | 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!
* 1671 - better separate setup from code under testKartik K. Agaram2015-06-271-2/+6
| | | | | Requires better support for special variable names in scenarios like 'screen' and 'console'.
* 1670Kartik K. Agaram2015-06-271-0/+10
|
* 1647Kartik K. Agaram2015-06-251-1/+2
|
* 1600Kartik K. Agaram2015-06-191-0/+1
|
* 1599Kartik K. Agaram2015-06-191-3/+3
|
* 1573Kartik K. Agaram2015-06-161-1/+1
|
* 1572Kartik K. Agaram2015-06-161-2/+5
|
* 1564 - a better way to support string literalsKartik K. Agaram2015-06-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our new heuristic is: all string literals are the same. If they contain newline before non-whitespace, we scan for comments assuming there might be code inside: foofoofoo [ ... # ']' inside comment ignored ] If they contain non-whitespace first, then we ignore comments assuming it's just a regular string: foofoofoo [abc#def] # valid string literal The big hole in this approach: foofoofoo [ # what about comments here containing ']'? ... # abc ] Currently this reads as a 'code comment' and terminates before the newline or '?' and will probably trigger errors down the line. Temporary workaround: don't start code strings with a comment on the same line as the '['. Eventually we'll tighten up the logic. We're still not using the new heuristic in scenarios, but that's up next.
* 1525Kartik K. Agaram2015-06-041-1/+1
|
* 1514 - cleaner way to show backspaces in fake keyboardKartik K. Agaram2015-05-301-2/+2
| | | | In the process we now support unicode in all mu strings!
* 1508Kartik K. Agaram2015-05-281-1/+1
| | | | Aaalmost there..
* 1505Kartik K. Agaram2015-05-281-3/+3
| | | | Fix messages on failed screen tests.
* 1491Kartik K. Agaram2015-05-271-0/+2
|
* 1488Kartik K. Agaram2015-05-271-3/+4
|
* 1483 - *really* check color screens in scenariosKartik K. Agaram2015-05-271-6/+42
| | | | | | | | | | | | | | | | | Required fixing two levels of bugs: a) The hack in tangle to drop initial comments a '%' directive.. b) ..was masking a bug where run_mu_scenario wasn't robust to initial comments. Mildly concerned that neither of the sub-issues have their own tests, but I'm just removing hacks, and writing tests for that throwaway function like run_mu_scenario seems pointless. Instead I've solved the problem by disallowing comments before '%' directives. I've also taken this opportunity to at least try to document the 'scenarios' and '%' directives at the first layer where they appear.
* 1479 - screen tests can check colorKartik K. Agaram2015-05-261-3/+48
| | | | | Unclear if filtering by color is the best interface. Adding the color attribute into the screen contents seems ugly.
* 1478Kartik K. Agaram2015-05-261-3/+4
|
* 1476 - fake screens support colorKartik K. Agaram2015-05-261-3/+3
|
* 1436Kartik K. Agaram2015-05-231-0/+4
|
* 1397 - support unicode in screen checksKartik K. Agaram2015-05-181-29/+100
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-21/+21
|
* 1374 - chessboard end-to-end test passes!Kartik K. Agaram2015-05-141-2/+43
| | | | | | | | | | After like 40 seconds (because of the 120-column screen), but whatever. The final bug was that clear-screen wasn't actually working right for fake screens. (The trace is too large for github, so I'm going to leave it out for now.)
* 1373Kartik K. Agaram2015-05-141-1/+4
|
* 1364 - trace call-stack when switching routinesKartik K. Agaram2015-05-131-1/+1
| | | | Drop the #$%# 'encapsulated' stack ADT.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-16/+13
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-14/+17
| | | | | | | | | | | | | | | 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.
* 1353Kartik K. Agaram2015-05-121-1/+4
|
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-2/+2
| | | | | | | | | 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-6/+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
* 1293 - start porting the chessboard app overKartik K. Agaram2015-05-061-0/+1
| | | | | | | | | Just to put all our new test primitives through their paces, and iron out any kinks. Just the one chessboard scenario is taking 1.5-2.5x all the tests we've written so far. But we're starting from a faster baseline, that was the point of the C++ port. I also have -O3 optimizations in my back-pocket.
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+128
I've tried to update the Readme, but there are at least a couple of issues.