diff options
| author | Kartik Agaram <vc@akkartik.com> | 2020-03-14 01:03:30 -0700 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2020-03-14 01:03:30 -0700 |
| commit | b7b24ec242b67614e0ab01b681cdfd90b28a4095 (patch) | |
| tree | 1a209058409dddb9ed15ef614e9a91b23c2574f5 | |
| parent | 9f589350cf7b5bc9696c86f53d63fcc298d9bb14 (diff) | |
| download | mu-b7b24ec242b67614e0ab01b681cdfd90b28a4095.tar.gz | |
6142
| -rw-r--r-- | README.md | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/README.md b/README.md index 56132726..962dd251 100644 --- a/README.md +++ b/README.md @@ -327,12 +327,15 @@ Strings are the only place where a SubX word is allowed to contain spaces. That should be enough information for writing SubX programs. The `apps/` directory provides some fodder for practice in the `apps/ex*.subx` files, -giving a more gradual introduction to SubX features. This repo includes -binaries for all examples. At any commit, an example's binary should be -identical bit for bit with the result of translating the corresponding `.subx` -file. The binary should also be natively runnable on a Linux system running on -Intel x86 processors, either 32- or 64-bit. If either of these invariants is -broken it's a bug on my part. +giving a more gradual introduction to SubX features. In particular, you should +work through `apps/factorial4.subx`, which demonstrates all the above ideas in +concert. + +This repo includes binaries for all examples. At any commit, an example's +binary should be identical bit for bit with the result of translating the +corresponding `.subx` file. The binary should also be natively runnable on a +Linux system running on Intel x86 processors, either 32- or 64-bit. If either +of these invariants is broken it's a bug on my part. ## Running |