Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify text format standardization. #73

Merged
merged 4 commits into from
May 19, 2015
Merged

Clarify text format standardization. #73

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6b379cd
Clarify text format standardization.
jfbastien May 18, 2015
828a689
Standard text format, but only for tooling.
jfbastien May 18, 2015
71f87c2
Rebase.
jfbastien May 19, 2015
8c32721
Address Luke and Alon's comments.
jfbastien May 19, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions V1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"represent" is a loaded word; how about s/represent disassembled binaries/present binary code/?

format.
* Browsers will not parse the textual format in order to implement WebAssembly
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "in order to implement..." part might be removed? Not sure what it adds, and it seems a little confusing in that it draws focus. Or is there something crucial there that I am missing?

Or, perhaps "Browsers will not parse the textual format on web content", to clarify that they can do so in dev tools?

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
Expand Down