about summary refs log tree commit diff stats
path: root/fork.mu
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-05-07 15:06:53 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-05-07 15:29:13 -0700
commit0487a30e7078861ed7de42bdb21b5c71fb9b54a1 (patch)
treef7ccc4040b510403da90477947c1cf07ea91b627 /fork.mu
parent94fa5c95ad9c8beead183bb7c4b88c7c2c7ca6ec (diff)
downloadmu-0487a30e7078861ed7de42bdb21b5c71fb9b54a1.tar.gz
1298 - better ingredient/product handling
All primitives now always write to all their products. If a product is
not used that's fine, but if an instruction seems to expect too many
products mu will complain.

In the process, many primitives can operate on more than two ingredients
where it seems intuitive. You can add or divide more than two numbers
together, copy or negate multiple corresponding locations, etc.

There's one remaining bit of ugliness. Some instructions like
get/get-address, index/index-address, wait-for-location, these can
unnecessarily load values from memory when they don't need to.

Useful vim commands:
  %s/ingredients\[\([^\]]*\)\]/ingredients.at(\1)/gc
  %s/products\[\([^\]]*\)\]/products.at(\1)/gc
  .,$s/\[\(.\)]/.at(\1)/gc
Diffstat (limited to 'fork.mu')
-rw-r--r--fork.mu6
1 files changed, 4 insertions, 2 deletions
diff --git a/fork.mu b/fork.mu
index eb1a2ca1..1e3bac99 100644
--- a/fork.mu
+++ b/fork.mu
@@ -3,7 +3,8 @@ recipe main [
   default-space:address:array:location <- new location:type, 2:literal
   x:integer <- copy 34:literal
   {
-    $print x:integer
+    $print x:integer, [
+]
     loop
   }
 ]
@@ -12,7 +13,8 @@ recipe thread2 [
   default-space:address:array:location <- new location:type, 2:literal
   y:integer <- copy 35:literal
   {
-    $print y:integer
+    $print y:integer, [
+]
     loop
   }
 ]