From 70f70118f468b51ac14b7e992b0ec941c3a50d4d Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Wed, 28 Oct 2015 18:19:41 -0700 Subject: 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!) --- 072scenario_screen.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '072scenario_screen.cc') 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") { -- cgit 1.4.1-2-gfad0