OBD:Data types: Difference between revisions

m
→‎Appearance: note on subtypes
m (more...)
m (→‎Appearance: note on subtypes)
Line 9: Line 9:
:Same for longs with high bits/bytes and more generally, IDs.
:Same for longs with high bits/bytes and more generally, IDs.
Ideally, the labels for recurring bitsets and ID fields should be hardcoded, but it's OK to have them in struct defs ATM.
Ideally, the labels for recurring bitsets and ID fields should be hardcoded, but it's OK to have them in struct defs ATM.
:Sorta "subtypes" for short, long, etc, depending on what function the field corresponds to (a ''lot'' of subtypes)...
::No hurry for that...




----
----
==Resource links==
==Resource links==
===Level ID===
===Level ID===