Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Back in the day when it mattered, we did it like
#define BV00 (1 << 0)
#define BV01 (1 << 1)
#define BV02 (1 << 2)
#define BV03 (1 << 3)
...etc
#define IS_SET(flag, bit) ((flag) & (bit))
#define SET_BIT(var, bit) ((var) |= (bit))
#define REMOVE_BIT(var, bit) ((var) &= ~(bit))
#define TOGGLE_BIT(var, bit) ((var) ^= (bit))
....then...
#define MY_FIRST_BOOLEAN BV00
SET_BIT(myFlags, MY_FIRST_BOOLEAN)
True.
Well storing that would only take half a bit.
if wasting a byte or seven matters to you, then then you need to be working in a lower level language.
It's 7 bits....
Pay attention. 🤪
It's far more often stored in a word, so 32-64 bytes, depending on the target architecture. At least in most languages.
...or you can be coding assembler - it's all just bits to me
The 8-bit Intel 8051 family provides a dedicated bit-addressable memory space (addresses 20h-2Fh in internal RAM), giving 128 directly addressable bits. Used them for years. I'd imagine many microcontrollers have bit-width variables.
bit myFlag = 0;
Or even return from a function:
bit isValidInput(unsigned char input) { // Returns true (1) if input is valid, false (0) otherwise return (input >= '0' && input <= '9'); }
We could go the other way as well: TI's C2000 microcontroller architecture has no way to access a single byte, let alone a bit. A Boolean is stored in 16-bits on that one.
And, you can have pointers to bits!
Nothing like that in ARM. Even microcontrollers have enough RAM that nobody cares, I guess.
ARM has bit-banding specifically for this. I think it’s limited to M-profile CPUs (e.g. v7-M) but I’ve definitely used this before. It basically creates a 4-byte virtual address for every bit in a region. So the CPU itself can’t “address” a bit but it can access an address backed by only 1 bit of SRAM or registers (this is also useful to atomically access certain bits in registers without needing to use SW atomics).
Now store the numbers (array):
0 0 0 1 0 1 1 2
think 8 bytes???
Does anybody ever figure in parity when comparing bit sizes and all that jazz or are we only ever concerned with storage space?
Weird how I usually learn more from the humor communities than the serious ones... 😎
just like electronic components, they sell the gates by the chip with multiple gates in them because it's cheaper
That's a good analogy.
7 Shades of Truth
Redundancy is nice in the event of bitflip errors
Is the redundancy used for bools? I mean in actual practice.
iunno ¯_(ツ)_/¯
Wait till you realise the size of SSD sectors
