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!)

1 files changed, 4 insertions, 2 deletions

diff --git a/052tangle.cc b/052tangle.cc
index 2c393a31..7995e501 100644
--- a/052tangle.cc
+++ b/052tangle.cc
@@ -35,7 +35,8 @@ Fragments_used.clear();
 :(before "End Command Handlers")
 else if (command == "before") {
   string label = next_word(in);
-  recipe tmp = slurp_body(in);
+  recipe tmp;
+  slurp_body(in, tmp);
   if (is_waypoint(label))
     Before_fragments[label].steps.insert(Before_fragments[label].steps.end(), tmp.steps.begin(), tmp.steps.end());
   else
@@ -43,7 +44,8 @@ else if (command == "before") {
 }
 else if (command == "after") {
   string label = next_word(in);
-  recipe tmp = slurp_body(in);
+  recipe tmp;
+  slurp_body(in, tmp);
   if (is_waypoint(label))
     After_fragments[label].steps.insert(After_fragments[label].steps.begin(), tmp.steps.begin(), tmp.steps.end());
   else