about summary refs log tree commit diff stats
path: root/channel.mu
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2016-03-08 01:30:14 -0800
committerKartik K. Agaram <vc@akkartik.com>2016-03-08 01:46:47 -0800
commit1ead356219bb2eb59487d1012f837bd07ec336f5 (patch)
treeaf15f390b81e4d6b3e0940c5756a0d7fd1060bb5 /channel.mu
parent27ba0937a3747684f299bb7a8b3cdd0fbb689db3 (diff)
downloadmu-1ead356219bb2eb59487d1012f837bd07ec336f5.tar.gz
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.
Diffstat (limited to 'channel.mu')
-rw-r--r--channel.mu6
1 files changed, 3 insertions, 3 deletions
diff --git a/channel.mu b/channel.mu
index 54486957..6e948da0 100644
--- a/channel.mu
+++ b/channel.mu
@@ -1,6 +1,6 @@
 # example program: communicating between routines using channels
 
-recipe producer chan:address:shared:channel -> chan:address:shared:channel [
+def producer chan:address:shared:channel -> chan:address:shared:channel [
   # produce characters 1 to 5 on a channel
   local-scope
   load-ingredients
@@ -18,7 +18,7 @@ recipe producer chan:address:shared:channel -> chan:address:shared:channel [
   }
 ]
 
-recipe consumer chan:address:shared:channel -> chan:address:shared:channel [
+def consumer chan:address:shared:channel -> chan:address:shared:channel [
   # consume and print integers from a channel
   local-scope
   load-ingredients
@@ -32,7 +32,7 @@ recipe consumer chan:address:shared:channel -> chan:address:shared:channel [
   }
 ]
 
-recipe main [
+def main [
   local-scope
   chan:address:shared:channel <- new-channel 3
   # create two background 'routines' that communicate by a channel