I've seen this referred to as a "packed" field in some cases.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
Yeah that’s a good suggestion. A common way to refer to low-level memory structures e.g. C structs. Bit packing, padding, and alignment.
I usually call it a bit stream or a bit field.
Shot name is stored as a 32-bit big endian integer where:
- The first 15 bits stores the sequence number.
- The last 17 bits stores the shot number.
(time) Multiplex would be if you only had a single 17bit field and alternate the two elements.
Time-division isn't the only kind of multiplexing ... but I guess most of the others already have more specific names.
I'd use 'encoded as 15:17', or 'packed' is fine here as well.
I'd also recommend being explicit about which 15 and 17 bits are used rather than using 'first' and 'last', because that may mean different things depending on the platform endianness. You could say 'Bits 0:14 store the sequence number, while bits 15:31 store the shot number'. That makes it far easier to reason about how to access each piece of data in the combined 32 bits.
I suppose multiplexing could be considered the right name.. multiplexing is putting two signals into a single one. So by the example, if you pack 15 and 17 into a single 32 bit, it's kind of multiplexing.
Especially if you send it as one thing, and unpack it later, which would be the demultiplexing