about summary refs log tree commit diff stats
path: root/screen.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 /screen.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 'screen.mu')
-rw-r--r--screen.mu2
1 files changed, 1 insertions, 1 deletions
diff --git a/screen.mu b/screen.mu
index 99efc9ce..89782489 100644
--- a/screen.mu
+++ b/screen.mu
@@ -3,7 +3,7 @@
 # The zero screen below means 'use the real screen'. Tests can also use fake
 # screens.
 
-recipe main [
+def main [
   open-console
   10:character <- copy 97/a
   print 0/screen, 10:character/a, 2/red