about summary refs log tree commit diff stats
path: root/050scenario.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1846Kartik K. Agaram2015-07-251-1/+1
|
* 1845 - never ever redefine the scenario's recipeKartik K. Agaram2015-07-251-2/+19
| | | | | | A couple of times now I've accidentally named a scenario the same thing as a recipe inside it that I define using 'run' or something. The resulting infinite loop is invariably non-trivial to debug.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-13/+13
| | | | | | | | | 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.
* 1796 - temporarily undo 1795Kartik K. Agaram2015-07-161-1/+1
| | | | | Debugging simulated-screen support is taking too long, and I suddenly have a few higher priorities.
* 1795 - still debugging screen-in-screen renderingKartik K. Agaram2015-07-161-1/+1
| | | | I'm writing to location 'screen' somehow that's not the raw location.
* 1793 - rudimentary sandboxing for scenarios in the environmentKartik K. Agaram2015-07-151-1/+1
|
* 1754Kartik K. Agaram2015-07-101-1/+1
|
* 1751 - sluggishness fixedKartik K. Agaram2015-07-101-1/+1
| | | | | | | Ah, I was indeed double-rendering, but somehow it was still hard to see the problem past that preliminary diagnosis. Still two failing tests to fix.
* 1746 - load file and run a single testKartik K. Agaram2015-07-101-7/+6
| | | | $ ./mu test run-instruction-and-print-warnings
* 1745 - hoist warning/response strings out of editor-dataKartik K. Agaram2015-07-101-1/+1
| | | | | | | | | | Still ugly as hell. Some tests failing, but they're most likely wrong. We need to test cursor positioning at the level of the environment and take it away from the responsibilities of individual editors. Also bring back the line at the bottom of each editor. The non-test run ('main' in edit.mu) is completely borked. Sluggish as hell, and I can't seem to switch focus to the sandbox editor.
* 1743Kartik K. Agaram2015-07-091-1/+1
|
* 1721 - hide warnings inside interactive routinesKartik K. Agaram2015-07-081-10/+20
| | | | | | | | | | 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-9/+9
| | | | | | | 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!
* 1672 - begin support for multiple editors at onceKartik K. Agaram2015-06-281-1/+1
|
* 1671 - better separate setup from code under testKartik K. Agaram2015-06-271-5/+13
| | | | | Requires better support for special variable names in scenarios like 'screen' and 'console'.
* 1668 - there's a bug in CHECK_TRACE_DOESNT_CONTAINKartik K. Agaram2015-06-271-1/+3
| | | | For starters start making the test fail when building until layer 41.
* 1621Kartik K. Agaram2015-06-221-1/+1
| | | | | | | | repl.mu now passing again. But still I have concerns: a) Doubling backslashes in tests. Hard to tell how many levels to add. b) I think the read-key interface needs to go. But then how do we handle send-keys-to-channel and other flows like that in the chessboard app?
* 1620Kartik K. Agaram2015-06-221-1/+3
| | | | | | | | chessboard finally passing all its tests. What made this hard was that for some reason one of the background routines in the main chessboard test wasn't terminating like it used to. And so it was polluting *later* tests. Just clean up that source of contamination for now. Later we'll think about routine termination.
* 1598Kartik K. Agaram2015-06-191-2/+5
| | | | | Some tests weren't actually running for the past 5 days. Performed 5 why's.
* 1569Kartik K. Agaram2015-06-161-0/+1
|
* 1566 - fake mouse clicks in scenariosKartik K. Agaram2015-06-151-1/+1
|
* 1565Kartik K. Agaram2015-06-141-31/+4
|
* 1564 - a better way to support string literalsKartik K. Agaram2015-06-141-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 1498Kartik K. Agaram2015-05-281-8/+20
| | | | Cleaner to delegate as much as possible to slurp_quoted.
* 1497 - 2 boneheaded bugs in parsing scenariosKartik K. Agaram2015-05-281-6/+30
|
* 1494Kartik K. Agaram2015-05-271-1/+1
|
* 1491Kartik K. Agaram2015-05-271-0/+3
|
* 1483 - *really* check color screens in scenariosKartik K. Agaram2015-05-271-1/+2
| | | | | | | | | | | | | | | | | 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.
* 1475Kartik K. Agaram2015-05-261-5/+16
|
* 1434 - support all unicode spacesKartik K. Agaram2015-05-231-4/+22
|
* 1417 - draft zoom levels in tracesKartik K. Agaram2015-05-211-3/+3
|
* 1416Kartik K. Agaram2015-05-211-12/+12
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-14/+0
|
* 1412 - starting to clean up trace formatKartik K. Agaram2015-05-211-2/+2
| | | | | Many features of my trace layer were just inherited blindly from wart but lying unused in this project. Throw them out while we're at it.
* 1401 - shave 80% off chessboard test timeKartik K. Agaram2015-05-181-1/+1
| | | | It was all going to laboriously writing out 300+ MB to disk.
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-14/+14
|
* 1387Kartik K. Agaram2015-05-161-3/+3
|
* 1374 - chessboard end-to-end test passes!Kartik K. Agaram2015-05-141-1/+1
| | | | | | | | | | 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.)
* 1364 - trace call-stack when switching routinesKartik K. Agaram2015-05-131-1/+1
| | | | Drop the #$%# 'encapsulated' stack ADT.
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-15/+15
| | | | ..now that we support non-integers.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-10/+10
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-10/+10
| | | | | | | | | | | | | | | 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.
* 1355Kartik K. Agaram2015-05-121-0/+11
|
* 1343Kartik K. Agaram2015-05-111-2/+2
|
* 1327 - better error handling in chessboardKartik K. Agaram2015-05-101-2/+11
| | | | | Also a bugfix in break to label, because I noticed the screen wasn't being cleaned up on quit.
* 1323 - keyboard supports backspace and newlineKartik K. Agaram2015-05-101-0/+1
| | | | | | 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
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-6/+6
| | | | | | | | | 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-19/+19
| | | | | | | | | | | | | | | | | | | 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/+477
I've tried to update the Readme, but there are at least a couple of issues.