diff options
| author | Brad Nelson <flagxor@gmail.com> | 2016-10-31 00:32:14 -0700 |
|---|---|---|
| committer | Seth Thompson <s3th.thompson@gmail.com> | 2016-10-31 00:32:14 -0700 |
| commit | 111d30f81e5b8ab26625d7c505f2c473c6667e8d (patch) | |
| tree | d433f146b49ce07bfd775ce8069be35b79345981 /TextFormat.md | |
| parent | 137ce2b65073244e756d07095d111b743a231c63 (diff) | |
| download | nanowasm-design-111d30f81e5b8ab26625d7c505f2c473c6667e8d.tar.gz | |
Move stars out of the title. (#853)
Diffstat (limited to 'TextFormat.md')
| -rw-r--r-- | TextFormat.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/TextFormat.md b/TextFormat.md index 1f25ca3..d852d41 100644 --- a/TextFormat.md +++ b/TextFormat.md @@ -96,7 +96,8 @@ story, a lightweight, optional "debug symbol" global section may be defined which associates names with each indexed entity and, when present, these names will be used in the text format projected from a binary WebAssembly module. -# Future design :unicorn: +# Future design +## :unicorn: An official text format capable of representing WebAssembly modules needs a way of encoding, in addition to function bodies: declarations, function @@ -123,4 +124,4 @@ There is no requirement to use JavaScript syntax; this format is not intended to The text format may not be uniquely representable. Multiple textual files will likley assemble to the same binary file. For example, whitespace shouldn't be significant and memory initialization can be broken out into smaller pieces in a text format. -The text format should be precise in that values that cannot be accurately represented in the binary format are considered invalid text. Floating-point numbers should therefore be represented as hexadecimal floating-point as specified by C99, C++17, and IEEE-754-2008 section 5.12.3. The textual format may be improved to also support more human-readable representations, but never at the cost of accurate representation.
\ No newline at end of file +The text format should be precise in that values that cannot be accurately represented in the binary format are considered invalid text. Floating-point numbers should therefore be represented as hexadecimal floating-point as specified by C99, C++17, and IEEE-754-2008 section 5.12.3. The textual format may be improved to also support more human-readable representations, but never at the cost of accurate representation. |
