about summary refs log tree commit diff stats
path: root/035call_ingredient.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2685Kartik K. Agaram2016-02-191-2/+2
| | | | | | | | | | | | | | | | Stack of plans for cleaning up replace_type_ingredients() and a couple of other things, from main problem to subproblems: include type names in the type_tree rather than in the separate properties vector make type_tree and string_tree real cons cells, with separate leaf nodes redo the vocabulary for dumping various objects: do we really need to_string and debug_string? can we have a version with *all* information? can we have to_string not call debug_string? This commit nibbles at the edges of the final task, switching from member method syntax to global function like almost everything else. I'm mostly using methods just for STL in this project.
* 2557 - type-check most ingredients ahead of timeKartik K. Agaram2016-01-121-2/+1
|
* 2608 - improve errors when static dispatch failsKartik K. Agaram2015-11-291-2/+2
|
* 2607 - resolve some edge cases in static dispatchKartik K. Agaram2015-11-291-0/+1
|
* 2488 - fix memory leaks from 2484Kartik K. Agaram2015-11-281-1/+0
|
* 2484Kartik K. Agaram2015-11-271-8/+3
| | | | | Eliminate one of several hacky type-check helpers; they've been proliferating lately.
* 2439 - bugfix: commandline ingredientsKartik K. Agaram2015-11-141-5/+10
|
* 2377 - stop using operator[] in mapKartik K. Agaram2015-11-061-6/+6
| | | | | | | | | | | | | | | | I'm still seeing all sorts of failures in turning on layer 11 of edit/, so I'm backing away and nailing down every culprit I run into. First up: stop accidentally inserting empty objects into maps during lookups. Commands run: $ sed -i 's/\(Recipe_ordinal\|Recipe\|Type_ordinal\|Type\|Memory\)\[\([^]]*\)\] = \(.*\);/put(\1, \2, \3);/' 0[1-9]* $ vi 075scenario_console.cc # manually fix up Memory[Memory[CONSOLE]] $ sed -i 's/\(Memory\)\[\([^]]*\)\]/get_or_insert(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe_ordinal\|Type_ordinal\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe\|Type\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* Now mu dies pretty quickly because of all the places I try to lookup a missing value.
* 2299 - check types of ingredients in callsKartik K. Agaram2015-10-281-1/+16
| | | | | | | | | | Still very incomplete: a) we perform the check at runtime b) tests for edit and sandbox apps no longer work; we can't fix them until we get type parameters in both containers and recipes (because list and list operations need to become generic).
* 2297Kartik K. Agaram2015-10-281-10/+10
|
* 2296 - record ingredient types on call stackKartik K. Agaram2015-10-281-0/+2
| | | | | As we perform type-checking earlier we'll delete these checks. But start with type-checking at run-time.
* 2295 - drop first-class recipes and continuationsKartik K. Agaram2015-10-281-4/+0
| | | | Making life too complex at this time.
* 2294Kartik K. Agaram2015-10-281-1/+5
| | | | Bah, sick of CALL and continuations.
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-8/+8
| | | | | | | 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.
* 2257Kartik K. Agaram2015-10-061-1/+6
|
* 2232Kartik K. Agaram2015-10-011-9/+20
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-4/+4
| | | | | | | | 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?
* 2205 - warn on missing ingredientKartik K. Agaram2015-09-181-0/+12
| | | | ..unless you explicitly ignore the found? result.
* 1923Kartik K. Agaram2015-08-021-3/+0
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-0/+3
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-5/+5
| | | | First step to reducing typing burden. Next step: inferring types.
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-2/+13
| | | | Also standardized warnings.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-3/+3
| | | | | | | 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!
* 1698Kartik K. Agaram2015-07-031-0/+116