Eldred Habert

If #635 is merged, this would look fine: ```asm struct Substatus [ SubStatus1:: db SubStatus2:: db SubStatus3:: db SubStatus4:: db SubStatus5:: db ] wPlayer:: dstruct Substatus ```

Given that semicolons are not part of any valid value here (symbols don't take them), we thankfully don't have this problem. I don't think we'll support semicolons in labels either,...

I don't like that syntax because it fails to convey which is the type and which is the name. Besides, we'd probably also want initializer syntax for ROM data. ```asm...

A development as far as this issue is concerned: since we have a website, we have a place where we could publish such specifications. Now that I have some time...

I wrote documentation on the SYM file format, but I'm less sure about the MAP one. It's currently still a moving target, and while following a somewhat systematic format, it's...

Since I'm about to make a PR that details additional behavior, what style do we want? What should the link point to, the specific test ROM's source, the ROM collection?...

Okay, I wasn't intending *exactly* on using a byte, but the more general idea of storing the length separately. Wasn't aware of Rust's behavior, which is basically what I'm shooting...

What's the status on this? There's been a lot of cleanup recently, we should survey the document on whether this has been fixed.

Section titles can be checked using some ungodly regexes, so I'll see to this this evening. ```bash sed -E 's,^.*([^

Another inconsistency we have is `(R)` vs. `(Read Only)`, and `(R/W)` vs. `(Read/Write)`. I suggest `(Read-only)` and `(Read/Write)` respectively, for clarity.