diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-03-10 14:51:04 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-03-10 14:51:04 -0800 |
| commit | eb0abedd1728dd61cd18555f2e6dbc66cb0a847d (patch) | |
| tree | c6b8ce58d0e60ce6675aac0918bd1fc2dc64923f | |
| parent | d81276ca33fcb5da42178d6279f0b7b26af1ad0b (diff) | |
| download | mu-eb0abedd1728dd61cd18555f2e6dbc66cb0a847d.tar.gz | |
2753
| -rw-r--r-- | Readme.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Readme.md b/Readme.md index 27d198e6..a0147b95 100644 --- a/Readme.md +++ b/Readme.md @@ -58,9 +58,9 @@ comprehend than programs as trees of expressions. Second, I've found that Literate Programming using layers makes assembly much more ergonomic. Third, labels for gotos turn out to be great waypoints to insert code at from future layers; when I tried to divide C programs into layers, I sometimes had to -split statements in two so I could insert code between them. They also seem a -promising representation for providing advanced mechanisms like continuations -and lisp-like macros. +split statements in two so I could insert code between them. Labels also seem +a promising representation for providing advanced mechanisms like +continuations and lisp-like macros. High level languages today seem to provide three kinds of benefits: expressiveness (e.g. nested expressions, classes), safety (e.g. type checking) |