diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-11-10 10:24:14 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-11-10 10:24:14 -0800 |
| commit | f116818c7c6e98a5d9bfa7058096b42df85d8e1c (patch) | |
| tree | ba3458a0c51f67c27c7347b1c5f5be2fc33965e2 /043space.cc | |
| parent | b771d375d3e11dcf3e6e55175f2ae128448177a7 (diff) | |
| download | mu-f116818c7c6e98a5d9bfa7058096b42df85d8e1c.tar.gz | |
3656
Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student.
Diffstat (limited to '043space.cc')
| -rw-r--r-- | 043space.cc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/043space.cc b/043space.cc index 409cd614..6c553661 100644 --- a/043space.cc +++ b/043space.cc @@ -222,7 +222,7 @@ if (curr.name == "local-scope") { rewrite_default_space_instruction(curr); } -//: todo: do this in a transform, rather than magically in the reply instruction +//: todo: do this in a transform, rather than magically in the return instruction :(after "Falling Through End Of Recipe") try_reclaim_locals(); :(after "Starting Reply") @@ -259,7 +259,7 @@ void try_reclaim_locals() { } :(code) -// is this reagent one of the values returned by the current (reply) instruction? +// is this reagent one of the values returned by the current (return) instruction? // is the corresponding ingredient saved in the caller? bool escaping(const reagent& r) { assert(Current_routine); // run-time only @@ -370,7 +370,7 @@ def main [ def f [ local-scope x:&:num <- new number:type - reply x:&:num + return x:&:num ] def main [ f # doesn't save result |