Thank you for making this + suggestion to make parser output more human-understandable about a-binary-parser-generator HOT 1 OPEN

oh man, I've not worked on this thing in years - having specs be self descriptive, and yield code that can be queried for this descriptions, sounds like a great idea! Although I don't know if I'm (ever?) going to have time to add that in. That said, with JavaScript having been significantly revised since I wrote this code, it might be interesting to revisit the generator and see if the new syntax makes a rewrite easier.

For something like the OpenType spec though having just the local description tends to break down fairly quickly: for the metadata fields a local description makes sense ("the maximum glyph ascent", "the number of name records in this table") but for real data things get much harder to unravel without the actual guiding documentation that determines the spec. (just knowing that a USHORT in a FeatureRecordData struct is an offset value in a LookupRecord, for instance, does not tell us much more than only that, we still need the proper documentation to figure out what that means =)

from a-binary-parser-generator.