From 6b379cd9b38f5b7877237121455bc95631bb76bb Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Mon, 18 May 2015 11:30:38 -0700 Subject: [PATCH 1/4] Clarify text format standardization. --- V1.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/V1.md b/V1.md index ae7a6d0b..a0401c4d 100644 --- a/V1.md +++ b/V1.md @@ -73,8 +73,14 @@ precise descriptions of: * Presentation in browser devtools when source maps aren't present (which is necessarily the case with v.1). * Writing WebAssembly code directly for reasons including pedagogical, experimental, debugging, or optimization. -* The text format is equivalent and isomorphic to the [binary format](V1.md#binary-format), see notes - there. +* The text format is equivalent and isomorphic to the + [binary format](V1.md#binary-format), see notes there. +* The text format will be standardized, but only for tooling purposes: + * Compilers will support this format for `.S` and inline assembly. + * Debuggers and profilers will represent disassembled binaries using this + format. + * Browsers will not parse the textual format in order to implement WebAssembly + semantics. * Given that the code representation is actually an AST, the syntax would contain nested statements and expressions (instead of the linear list of instructions most assembly languages have). * There is no requirement to use JS syntax; this format is not intended to be evaluated or translated From 828a6898cc34aabcb688b89e6e2861d0a23479cf Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Mon, 18 May 2015 12:36:41 -0700 Subject: [PATCH 2/4] Standard text format, but only for tooling. --- V1.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/V1.md b/V1.md index a0401c4d..ad6d41a0 100644 --- a/V1.md +++ b/V1.md @@ -73,8 +73,7 @@ precise descriptions of: * Presentation in browser devtools when source maps aren't present (which is necessarily the case with v.1). * Writing WebAssembly code directly for reasons including pedagogical, experimental, debugging, or optimization. -* The text format is equivalent and isomorphic to the - [binary format](V1.md#binary-format), see notes there. +* The text format is equivalent and isomorphic to the [binary format](V1.md#binary-format), see notes there. * The text format will be standardized, but only for tooling purposes: * Compilers will support this format for `.S` and inline assembly. * Debuggers and profilers will represent disassembled binaries using this From 71f87c27de8ae1a7bbc562bd031896429a3a8006 Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Tue, 19 May 2015 08:06:10 -0700 Subject: [PATCH 3/4] Rebase. --- V1.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/V1.md b/V1.md index ad6d41a0..a0401c4d 100644 --- a/V1.md +++ b/V1.md @@ -73,7 +73,8 @@ precise descriptions of: * Presentation in browser devtools when source maps aren't present (which is necessarily the case with v.1). * Writing WebAssembly code directly for reasons including pedagogical, experimental, debugging, or optimization. -* The text format is equivalent and isomorphic to the [binary format](V1.md#binary-format), see notes there. +* The text format is equivalent and isomorphic to the + [binary format](V1.md#binary-format), see notes there. * The text format will be standardized, but only for tooling purposes: * Compilers will support this format for `.S` and inline assembly. * Debuggers and profilers will represent disassembled binaries using this From 8c32721a1968156748974f9be002e89ac26f9c69 Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Tue, 19 May 2015 11:41:13 -0700 Subject: [PATCH 4/4] Address Luke and Alon's comments. --- V1.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/V1.md b/V1.md index a0401c4d..4779b816 100644 --- a/V1.md +++ b/V1.md @@ -77,10 +77,9 @@ precise descriptions of: [binary format](V1.md#binary-format), see notes there. * The text format will be standardized, but only for tooling purposes: * Compilers will support this format for `.S` and inline assembly. - * Debuggers and profilers will represent disassembled binaries using this - format. - * Browsers will not parse the textual format in order to implement WebAssembly - semantics. + * Debuggers and profilers will present binary code using this textual format. + * Browsers will not parse the textual format on regular web content in order + to implement WebAssembly semantics. * Given that the code representation is actually an AST, the syntax would contain nested statements and expressions (instead of the linear list of instructions most assembly languages have). * There is no requirement to use JS syntax; this format is not intended to be evaluated or translated