diff options
| author | titzer <titzer@google.com> | 2016-10-11 17:47:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-11 17:47:02 +0200 |
| commit | e49fc18b684c953e3d920dcfc4bfce8ede9268dd (patch) | |
| tree | db3843485e77013c763c4dbf27de9ab3711e371b /TextFormat.md | |
| parent | acfa2e2f6e02bb4f9c46a03882b72fb43e410eca (diff) | |
| download | nanowasm-design-e49fc18b684c953e3d920dcfc4bfce8ede9268dd.tar.gz | |
Structured stack (#813)
* Rename AstSemantics.md to Semantics.md
* Rewrite Semantics for structured stack machine
* Update control instructions
* Update nop
* More tweaks
* Update README.md
* Update Semantics.md
* Update Semantics.md
* Address @rossberg-chromium comments
Diffstat (limited to 'TextFormat.md')
| -rw-r--r-- | TextFormat.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/TextFormat.md b/TextFormat.md index 2318a61..d6d3dc0 100644 --- a/TextFormat.md +++ b/TextFormat.md @@ -17,7 +17,7 @@ The text format will be standardized, but only for tooling purposes: implement WebAssembly semantics. Given that the code representation is actually an -[Abstract Syntax Tree](AstSemantics.md), the syntax would contain nested +[Abstract Syntax Tree](Semantics.md), the syntax would contain nested statements and expressions (instead of the linear list of instructions most assembly languages have). @@ -50,7 +50,7 @@ readability will therefore factor into standardizing a text format. There are, however, prototype syntaxes which are used to bring up WebAssembly: it's easier to develop using a text format than it is with a binary format, even if the ultimate WebAssembly format will be binary. Most of these prototypes use [s-expressions][] because they -can easily represent expression trees and [ASTs](AstSemantics.md) (as opposed to CFGs) +can easily represent expression trees and [ASTs](Semantics.md) (as opposed to CFGs) and don't have much of a syntax to speak of (avoiding syntax bikeshed discussions). [s-expressions]: https://en.wikipedia.org/wiki/S-expression |