Well, it was technically made mostly of cpp macros

Because in C it is undefined behaviour

In C 'a' is int for standard, in C++ is char

The size of an int is platform dependant in C

The size of an int is platform dependant in C

The size of an int is platform dependant in C

True but chars are mainly considered unicode

On avr sizeof('a') return 2 not 4

Here we go again, booting in 10 bytes from a disk on avr☺️

huh?

On modern day systems within cpp

True but chars are mainly considered unicode

Char is One byte in C and One byte is minimal addressable value, generally 8bit but in some dsp can be 16bits

Look at your compiler output

one byte is the minimal adressable size? Pretty sure that there are exotic archs with other sizes

but putting kanji into a padded char, is UB

also, in an array it wont be padded

Its allowed, it'll change the pad byte as its not padded -> its unicode

UC characters are quite useful in exploitation, even in web areas where there are polymorphic uc characters some uc characters are harmless by itself but become harmful when taken as ascii(which something thats written in like cpp likely would) uc characters are pain

不是要把，只需要该我们的程序

You see early CPP moving to unicode, others that copy from it seeing 'padding' and replicating that, then both upgrading to arrays and stuff and all of the sudden moving into full ascii again

You see early CPP moving to unicode, others that copy from it seeing 'padding' and replicating that, then both upgrading to arrays and stuff and all of the sudden moving into full ascii again

'Hey they output 0041 .. I should do that too'

and I laugh my ass off twice when some indian asks me how to start in kernel dev on linux