about summary refs log tree commit diff stats
path: root/chessboard.mu
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2016-04-27 17:59:46 -0700
committerKartik K. Agaram <vc@akkartik.com>2016-04-27 17:59:46 -0700
commite32a6a02ee6a14cd85c715979503a58b0d661085 (patch)
tree5fdc2bca211cd05bb66f7816eec1e42aed4e441c /chessboard.mu
parent612c48da330ed2814ee19f7e3f623e8946b200c8 (diff)
downloadmu-e32a6a02ee6a14cd85c715979503a58b0d661085.tar.gz
2878
Diffstat (limited to 'chessboard.mu')
-rw-r--r--chessboard.mu7
1 files changed, 1 insertions, 6 deletions
diff --git a/chessboard.mu b/chessboard.mu
index 9bd5adef..7ead26cb 100644
--- a/chessboard.mu
+++ b/chessboard.mu
@@ -9,16 +9,11 @@ def main [
   # In mu it is good form (though not required) to explicitly show the
   # hardware you rely on.
   #
-  # The chessboard also returns the same keyboard and screen objects. In mu it
-  # is good form to not modify ingredients of a function unless they are also
-  # results. Here we clearly modify both keyboard and screen, so we return
-  # both.
-  #
   # Here the console and screen are both 0, which usually indicates real
   # hardware rather than a fake for testing as you'll see below.
   chessboard 0/screen, 0/console
 
-  close-console  # cleanup screen, keyboard and mouse
+  close-console  # clean up screen, keyboard and mouse
 ]
 
 ## But enough about mu. Here's what it looks like to run the chessboard program.