2735 - define recipes using 'def'

I'm dropping all mention of 'recipe' terminology from the Readme. That
way I hope to avoid further bike-shedding discussions while I very
slowly decide on the right terminology with my students.

I could be smarter in my error messages and use 'recipe' when code uses
it and 'function' otherwise. But what about other words like ingredient?
It would all add complexity that I'm not yet sure is worthwhile. But I
do want separate experiences for veteran programmers reading about Mu on
github and for people learning programming using Mu.

1 files changed, 4 insertions, 4 deletions

diff --git a/063wait.cc b/063wait.cc
index c57f6b28..2d0e2d8d 100644
--- a/063wait.cc
+++ b/063wait.cc
@@ -4,14 +4,14 @@
 //: operate.
 
 :(scenario wait_for_location)
-recipe f1 [
+def f1 [
   1:number <- copy 0
   start-running f2
   wait-for-location 1:number
   # now wait for f2 to run and modify location 1 before using its value
   2:number <- copy 1:number
 ]
-recipe f2 [
+def f2 [
   1:number <- copy 34
 ]
 # if we got the synchronization wrong we'd be storing 0 in location 2
@@ -65,14 +65,14 @@ for (long long int i = 0; i < SIZE(Routines); ++i) {
 //: also allow waiting on a routine to stop running
 
 :(scenario wait_for_routine)
-recipe f1 [
+def f1 [
   1:number <- copy 0
   12:number/routine <- start-running f2
   wait-for-routine 12:number/routine
   # now wait for f2 to run and modify location 1 before using its value
   3:number <- copy 1:number
 ]
-recipe f2 [
+def f2 [
   1:number <- copy 34
 ]
 +schedule: f1