diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-10-28 18:19:41 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-10-28 18:26:05 -0700 |
| commit | 70f70118f468b51ac14b7e992b0ec941c3a50d4d (patch) | |
| tree | 07749a54af09d9bfbeb93b7b52dc4a175ed6a886 /072scenario_screen.cc | |
| parent | b69daf785df8dee56f851ce9d6dd38d7779a04ca (diff) | |
| download | mu-70f70118f468b51ac14b7e992b0ec941c3a50d4d.tar.gz | |
2306 - recipe headers
Once a student has gotten used to recipes and ingredients using the staged 'next-ingredient' approach there's no reason to avoid conventional function headers. As an added bonus we can now: a) check that all 'reply' instructions in a recipe are consistent b) deduce what to reply without needing to say so everytime c) start thinking about type parameters for recipes (generic functions!)
Diffstat (limited to '072scenario_screen.cc')
| -rw-r--r-- | 072scenario_screen.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/072scenario_screen.cc b/072scenario_screen.cc index f9536bc5..11151eac 100644 --- a/072scenario_screen.cc +++ b/072scenario_screen.cc @@ -137,7 +137,7 @@ const long long int SCREEN = Next_predefined_global_for_scenarios++; :(before "End Special Scenario Variable Names(r)") Name[r]["screen"] = SCREEN; -:(before "End Rewrite Instruction(curr)") +:(before "End Rewrite Instruction(curr, recipe result)") // rewrite `assume-screen width, height` to // `screen:address:screen <- new-fake-screen width, height` if (curr.name == "assume-screen") { |