mu/archive/1.vm/console.mu

# example program: reading events from keyboard or mouse
#
# Keeps printing 'a' until you press a key or click on the mouse.

def main [
  local-scope
  open-console
  {
    e:event, found?:bool <- check-for-interaction
    break-if found?
    print-character-to-display 97, 7/white
    loop
  }
  close-console
  $print e, 10/newline
]
1617 2015-06-22 06:37:49 +00:00			`# example program: reading events from keyboard or mouse`
			`#`
			`# Keeps printing 'a' until you press a key or click on the mouse.`

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. 2016-03-08 09:30:14 +00:00			`def main [`
2652 - fix issue #4 Thanks chriscool and achikin for reporting this bug. 2016-02-13 21:22:22 +00:00			`local-scope`
1618 2015-06-22 06:53:17 +00:00			`open-console`
1617 2015-06-22 06:37:49 +00:00			`{`
3483 2016-10-08 17:52:58 +00:00			`e:event, found?:bool <- check-for-interaction`
1880 - switch .mu files to new type-deducing idiom 2015-07-29 08:23:22 +00:00			`break-if found?`
1868 - start using naked literals everywhere First step to reducing typing burden. Next step: inferring types. 2015-07-28 21:33:22 +00:00			`print-character-to-display 97, 7/white`
1617 2015-06-22 06:37:49 +00:00			`loop`
			`}`
1618 2015-06-22 06:53:17 +00:00			`close-console`
2132 - support for ctrl + arrow keys 2015-09-03 02:18:24 +00:00			`$print e, 10/newline`
1617 2015-06-22 06:37:49 +00:00			`]`