diff options
| author | Alon Zakai <alonzakai@gmail.com> | 2015-11-18 15:38:28 -0800 |
|---|---|---|
| committer | Alon Zakai <alonzakai@gmail.com> | 2015-11-18 15:38:28 -0800 |
| commit | 7984ce54c4bc444b2942e2b2d6de3ca93d1601c8 (patch) | |
| tree | 42ce8c419ec3f2dca945a01b3ba593295c4608fb /TextFormat.md | |
| parent | ec06eeb0db1ce12dc05475eb8123281e55a8c879 (diff) | |
| parent | 149abe4fb3a018bdb81645509a55a631de410b5d (diff) | |
| download | nanowasm-design-7984ce54c4bc444b2942e2b2d6de3ca93d1601c8.tar.gz | |
Merge pull request #463 from WebAssembly/tf-consistency
Mention consistency on the web as a factor in the text format
Diffstat (limited to 'TextFormat.md')
| -rw-r--r-- | TextFormat.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/TextFormat.md b/TextFormat.md index c63ad84..0aacd16 100644 --- a/TextFormat.md +++ b/TextFormat.md @@ -22,7 +22,14 @@ statements and expressions (instead of the linear list of instructions most assembly languages have). There is no requirement to use JavaScript syntax; this format is not intended to -be evaluated or translated directly into JavaScript. +be evaluated or translated directly into JavaScript. There may also be +substantive reasons to use notation that is different than JavaScript (for +example, WebAssembly has a 32-bit integer type, and it should be represented +in the text format, since that is the natural thing to do for WebAssembly, +regardless of JavaScript not having such a type). On the other hand, +when there are no substantive reasons and the options are basically +bikeshedding, then it does make sense for the text format to match existing +conventions on the Web (for example, curly braces, as in JavaScript and CSS). The text format isn't uniquely representable. Multiple textual files can assemble to the same binary file, for example whitespace isn't relevant and memory initialization |