diff options
| author | JF Bastien <github@jfbastien.com> | 2015-08-31 10:24:21 -0700 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2015-08-31 10:24:21 -0700 |
| commit | 5256bb1573f2e70f73360c6c8bd00d1889d4ec0e (patch) | |
| tree | a5060d0b61b9b3afb934042a47d9bf0b2152ae0d | |
| parent | 0eb71ebfda33cc40767f3c21875663bf0a72c3c8 (diff) | |
| parent | 77d3112d02576d58cb48c865b8498a03fabe5342 (diff) | |
| download | nanowasm-design-5256bb1573f2e70f73360c6c8bd00d1889d4ec0e.tar.gz | |
Merge pull request #318 from WebAssembly/jfbastien-patch-1
Text format: not unique, but precise
| -rw-r--r-- | TextFormat.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/TextFormat.md b/TextFormat.md index 4bb9b3a..6619f6f 100644 --- a/TextFormat.md +++ b/TextFormat.md @@ -23,3 +23,13 @@ assembly languages have). There is no requirement to use JavaScript syntax; this format is not intended to be evaluated or translated directly into JavaScript. + +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 +can be broken out into smaller pieces in the text format. + +The text format is precise in that values that cannot be accurately represented in the +binary format are considered invalid text. Floating-point numbers are therefore +represented as hexadecimal floating-point as specified by the C99 standard, which +IEEE-754-2008 section 5.12.3 also specifies. The textual format may be improved to also +support more human-readable representations, but never at the cost of accurate representation. |