about summary refs log tree commit diff stats
path: root/011load.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1736 - stop refusing to reload code in the editorKartik K. Agaram2015-07-091-1/+1
| | | | All tests passing, but early layers are broken.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-20/+20
| | | | | | | 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!
* 1648Kartik K. Agaram2015-06-251-0/+2
|
* 1566 - fake mouse clicks in scenariosKartik K. Agaram2015-06-151-0/+3
|
* 1564 - a better way to support string literalsKartik K. Agaram2015-06-141-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 1518 - still horribly brokenKartik K. Agaram2015-06-011-0/+1
| | | | | | Just figured out why a first keystroke of backspace was sending me out for a spin: run_interactive needs all early exits that don't actually run anything to increment the current_step_index(). FML, this is lousy..
* 1483 - *really* check color screens in scenariosKartik K. Agaram2015-05-271-1/+1
| | | | | | | | | | | | | | | | | 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.
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-28/+28
|
* 1399 - better 'unknown type' warningsKartik K. Agaram2015-05-181-0/+1
| | | | | | | | Implement warnings for types without definitions without constraining where type definitions must appear. We also eliminate the anti-pattern where a change in layer 10 had its test in layer 11 (commit 1383).
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-4/+4
|
* 1385Kartik K. Agaram2015-05-161-0/+1
|
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-29/+29
| | | | ..now that we support non-integers.
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-7/+7
| | | | | | | | | 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 '[^ ]\['
* 1278 - support before/after tangle directivesKartik K. Agaram2015-05-051-30/+19
| | | | | No way to only insert code at a label in a specific recipe. Let's see how that goes.
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+328
I've tried to update the Readme, but there are at least a couple of issues.