diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-04-27 15:37:09 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-04-27 15:37:09 -0700 |
commit | 5109e78fab2e94059763eefaec93bd6649d22c1f (patch) | |
tree | adf53b2bff6745095e352d2fd147006998acb4ed /055recipe_header.cc | |
parent | e765f9e74abc81b738e8670c6d77d363894107b1 (diff) | |
download | mu-5109e78fab2e94059763eefaec93bd6649d22c1f.tar.gz |
2874
Be more consistent that 'return' is the name of the instruction, and 'reply' just a synonym. Maybe I should take it out. It wouldn't affect the recipe/ingredient terminology while I teach..
Diffstat (limited to '055recipe_header.cc')
-rw-r--r-- | 055recipe_header.cc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/055recipe_header.cc b/055recipe_header.cc index 9a4ec089..229a514d 100644 --- a/055recipe_header.cc +++ b/055recipe_header.cc @@ -361,7 +361,7 @@ void deduce_types_from_header(const recipe_ordinal r) { //: One final convenience: no need to say what to return if the information is //: in the header. -:(scenario reply_based_on_header) +:(scenario return_based_on_header) def main [ 1:number/raw <- add2 3, 5 ] @@ -426,7 +426,7 @@ def add2 a:number, b:number -> y:number, z:number [ +mem: storing 3 in location 1 +mem: storing -2 in location 2 -:(scenario reply_on_fallthrough_based_on_header) +:(scenario return_on_fallthrough_based_on_header) def main [ 1:number/raw <- add2 3, 5 ] @@ -438,7 +438,7 @@ def add2 x:number, y:number -> z:number [ +transform: instruction: reply {z: "number"} +mem: storing 8 in location 1 -:(scenario reply_on_fallthrough_already_exists) +:(scenario return_on_fallthrough_already_exists) def main [ 1:number/raw <- add2 3, 5 ] @@ -452,7 +452,7 @@ def add2 x:number, y:number -> z:number [ -transform: instruction: reply z:number +mem: storing 8 in location 1 -:(scenario reply_after_conditional_reply_based_on_header) +:(scenario return_after_conditional_reply_based_on_header) def main [ 1:number/raw <- add2 3, 5 ] |