Ensure that byte counts in tag CNs are consistent #18
Notifications
Due Date
No due date set.
Blocks
#17 Add an "Any" type to PDL
sashakoshka/hopp
Reference: sashakoshka/hopp#18
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We offset the byte count in integer tag CNs by -1 so that the format can squeeze in very large numbers up to 256 bits. This needs to be done for OTA and KTV and wherever else byte counts are stored in the CN (I think that's all). I'm not sure this is done consistently even with integers. The correct behavior needs to be written down in the protocol specification, and tested for in generated code and dynamic code.