From 149abe4fb3a018bdb81645509a55a631de410b5d Mon Sep 17 00:00:00 2001 From: Alon Zakai Date: Thu, 12 Nov 2015 13:51:08 -0800 Subject: mention consistency on the web as a factor in the text format, when bikeshedding --- TextFormat.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'TextFormat.md') diff --git a/TextFormat.md b/TextFormat.md index ab1b54a..2006fd2 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 -- cgit v1.2.3