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 /088file.mu | |
| 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 '088file.mu')
| -rw-r--r-- | 088file.mu | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/088file.mu b/088file.mu index de374f1f..fb03e8bf 100644 --- a/088file.mu +++ b/088file.mu @@ -86,7 +86,7 @@ def start-writing resources:&:resources, filename:text -> sink:&:sink:char, rout break-unless resources # fake file system routine-id <- start-running transmit-to-fake-file resources, filename, source - reply + return } # real file system file:num <- $open-file-for-writing filename @@ -136,7 +136,7 @@ def transmit-to-fake-file resources:&:resources, filename:text, source:&:source: loop-unless found? put-index *data, i, new-resource reset lock - reply + return } # if file didn't already exist, make room for it new-len:num <- add len, 1 |