gtypelib documentation misrepresents binary format
Submitted by fre..@..il.com
Link to original bug (#693102)
Description
The GObject Introspection Reference Manual contains a section documenting the Typelib binary format, unfortunately it consistently fails to document the presence of any reserved fields and padding. This makes the documentation useless for someone implementing a typelib parser.
For example the documentation claims that the header starts with:
gchar magic[16]; guint8 major_version; guint8 minor_version; guint16 n_entries;
when it actually starts with (referring to the C source)
gchar magic[16]; guint8 major_version; guint8 minor_version; guint16 reserved; guint16 n_entries;