about summary refs log tree commit diff stats
path: root/011load.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2293Kartik K. Agaram2015-10-271-3/+3
|
* 2287 - new lexing rulesKartik K. Agaram2015-10-271-5/+14
| | | | | Now we always consider words to be terminated at () and {}. We also always skip commas.
* 2286Kartik K. Agaram2015-10-271-1/+2
|
* 2285Kartik K. Agaram2015-10-261-2/+3
| | | | Still trying to come up with clean lexing rules.
* 2283 - represent each /property as a treeKartik K. Agaram2015-10-261-7/+2
|
* 2282Kartik K. Agaram2015-10-261-28/+28
| | | | | Switch format for tracing reagents in preparation for trees rather than arrays of properties.
* 2277 - reagents now have a tree of typesKartik K. Agaram2015-10-251-3/+4
|
* 2276Kartik K. Agaram2015-10-251-1/+1
|
* 2274Kartik K. Agaram2015-10-251-3/+0
|
* 2273 - start expanding the type systemKartik K. Agaram2015-10-251-6/+0
| | | | | | | | | | | | | | Current plan: parsing {x: foo, y: bar} syntax for reagents parsing s-expr syntax for properties supporting reverse instructions (<-) parsing s-expr syntax for recipe headers (recipe number number -> number) static dispatch generic functions type-checking higher-order functions type of delimited continuations? need more type information First step is done, and the second partially so.
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-11/+11
| | | | | | | 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.
* 2193Kartik K. Agaram2015-09-141-2/+2
|
* 2154 - check types only after loading all layersKartik K. Agaram2015-09-051-1/+0
| | | | | Follow-up to 2147, which switched transform_all to only run once, after loading all layers.
* 2150 - recipe! to explicitly redefineKartik K. Agaram2015-09-051-16/+46
| | | | | This will let me create separate 'main' recipes at each layer so people can interact with less featureful versions.
* 2149Kartik K. Agaram2015-09-051-2/+2
|
* 2134 - bugfix: comment terminated by eofKartik K. Agaram2015-09-021-5/+17
| | | | | I ran into this inside 'reload' when I left a trailing comment at the end of the editor.
* 2095Kartik K. Agaram2015-08-281-17/+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.
* 2054Kartik K. Agaram2015-08-211-0/+1
|
* 2039 - warn on unbalanced '['Kartik K. Agaram2015-08-191-14/+34
|
* 2022 - run sandboxes in separate routinesKartik K. Agaram2015-08-161-3/+4
|
* 1962Kartik K. Agaram2015-08-091-2/+2
| | | | Standardize test names.
* 1869 - rename the /deref property to /lookupKartik K. Agaram2015-07-281-2/+2
| | | | Should be a little bit more mnemonic.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-12/+12
| | | | First step to reducing typing burden. Next step: inferring types.
* 1846Kartik K. Agaram2015-07-251-3/+3
|
* 1845 - never ever redefine the scenario's recipeKartik K. Agaram2015-07-251-5/+8
| | | | | | 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-11/+14
| | | | | | | | | 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.
* 1841 - reenable old layersKartik K. Agaram2015-07-241-3/+14
|
* 1840Kartik K. Agaram2015-07-241-1/+0
|
* 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.