No.
So the idea is to have a new type FT_UINT128, and one new format
BASE_BYTES.
The BASE_HEX would display as it displays today -- there is no problem
printing two FT_UINT64 in HEX (high and low parts).
For FT_UNIT128 and BASE_DEC, 12 would be displayed as 12, and 100
would be display
On Mar 22, 2021, at 11:35 AM, Constantine Gavrilov wrote:
> There are two repeated patterns for this:
>
> 1. For capacity (bytes, blocks, etc.).
> 2. For units (how many times).
>
> So, I am thinking about two formats:
> 1. For bytes.
> 2. For units.
>
> The implementation would get high and l
During my work of NVME dissector, I have encountered many repeated
patterns of 16-byte integers.
I would like to add a 16-byte integer format, to avoid decoding these many
fields with custom functions.
Has it been considered before? Will such change be accepted or it is
utterly opposed on som
