about summary refs log tree commit diff stats
path: root/075scenario_console.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2241 - back to type-checking get-addressKartik K. Agaram2015-10-051-1/+1
| | | | | Now duplex-list is fully non-generic and only works with characters. But we'll fix that in a bit..
* 2232Kartik K. Agaram2015-10-011-2/+8
|
* 2149Kartik K. Agaram2015-09-051-1/+1
|
* 2105Kartik K. Agaram2015-08-291-1/+1
|
* 2101 - teach 'assume-console' about names of keysKartik K. Agaram2015-08-291-5/+76
| | | | I'm sick of using the 'replace-in-console' hack.
* 2095Kartik K. Agaram2015-08-281-16/+0
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-2/+4
| | | | | | | | | 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.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-7/+7
| | | | | | | 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/+2
| | | | | Requires better support for special variable names in scenarios like 'screen' and 'console'.
* 1630 - bring back replace-in-consoleKartik K. Agaram2015-06-231-0/+26
| | | | | | | | This takes away the need for multi-level escaping in scenario setup. Post-conditions like screen-should-contain are still an issue, though. Maybe each string literal should be able to specify escapes inside its syntax? Or at a per-instruction granularity?
* 1628Kartik K. Agaram2015-06-231-37/+37
|
* 1627 - new plan for backspaceKartik K. Agaram2015-06-231-3/+2
| | | | | | First, undo our existing hacky pseudo-support. Some repl tests currently breaking.
* 1625Kartik K. Agaram2015-06-231-1/+1
|
* 1621Kartik K. Agaram2015-06-221-7/+11
| | | | | | | | 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?
* 1616 - merging keyboard and events into 'console'Kartik K. Agaram2015-06-211-0/+192
Only core layers currently passing. Console apps are probably still broken.