pov: you found a linux user

thank you tom scott

a raccoon bite can be traded for a free vaccination at your GD

@EeveeEuphoria wtf!

didn’t pay the cat tax and so my cat went into foreclosure

hehe yeah (<- it is going to move to the Netherlands. again.)

@endrift didn’t vote but i do have an old windows 11 install on a separate drive

@jhwgh1968 my guess is that the 3 groups that would care are legacy codebase maintainers running some ancient vendor c from 20-30 years ago, c standards authors trying to support, who exactly?, and the designer of the deathstation 9k

@jhwgh1968 yeah POSIX requires CHAR_BIT=8 and so is every non-posix programming environment you’d write code for nowadays

@jhwgh1968 standard C was designed with CHAR_BIT ≥ 8 in mind. if a well formed program doesn’t work on CHAR_BIT 9 or, indeed, CHAR_BIT 64 that would be a spec bug

the size argument to malloc (same with any other size argument) is in multiples of char size. so it would allocate 80 octets of memory as expected

@jhwgh1968 the definition exists since c89, the first version of C standard

@jhwgh1968 then then it’s not a standard c compiler and i doubt media en/decoding runs particularly well on it either

@jhwgh1968 reading the source code of meson, it generates a test program that is basically just printf("%d", sizeof(char)); which is by definition 1