about summary refs log tree commit diff stats
path: root/mu.arc.t
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2014-10-10 23:49:53 -0700
committerKartik K. Agaram <vc@akkartik.com>2014-10-10 23:49:53 -0700
commitb1e7d8617afce3d0fe9c27ebe4e0168a468beb28 (patch)
tree09eb7350f0d5a0771632713e0dfca222de5dc451 /mu.arc.t
parent3861662698abb144b65478237d7a932180dfb710 (diff)
downloadmu-b1e7d8617afce3d0fe9c27ebe4e0168a468beb28.tar.gz
129
Diffstat (limited to 'mu.arc.t')
-rw-r--r--mu.arc.t6
1 files changed, 5 insertions, 1 deletions
diff --git a/mu.arc.t b/mu.arc.t
index ee32202d..a784709d 100644
--- a/mu.arc.t
+++ b/mu.arc.t
@@ -163,7 +163,11 @@
 ; various metadata in the rest. In this first example the only metadata is types:
 ; 'integer' for a memory location containing an integer, and 'literal' for a
 ; value included directly in code. (Assembly languages traditionally call them
-; 'immediate' operands.)
+; 'immediate' operands.) In the future a simple tool will check that the types
+; line up as expected in each op. A different tool might add types where they
+; aren't provided. Instead of a monolithic compiler I want to build simple,
+; lightweight tools that can be combined in various ways, say for using
+; different typecheckers in different subsystems.
 
 (reset)
 (new-trace "literal")