Ok, let’s get truly pedantic. After reading this, this and this, I’m pretty confident that I understand the intention behind both Standards. So, doing reinterpret_cast from std::uint8_t* to char* and then dereferencing the resulting pointer is safe and portable and is explicitly permitted by [basic.lval]. However, doing reinterpret_cast from char* to std::uint8_t* and then dereferencing … Read more
int8_t is a typedef for an integer type with the required characteristics: pure 2’s-complement representation, no padding bits, size of exactly 8 bits. For most (perhaps all) compilers, that means it’s going to be a typedef for signed char.(Because of a quirk in the definition of the term signed integer type, it cannot be a … Read more
If it exists, uint8_t must always have the same width as unsigned char. However, it need not be the same type; it may be a distinct extended integer type. It also need not have the same representation as unsigned char; for instance, the bits could be interpreted in the opposite order. This is a silly … Read more
It doesn’t really print a blank, but most probably the ASCII character with value 5, which is non-printable (or invisible). There’s a number of invisible ASCII character codes, most of them below value 32, which is the blank actually. You have to convert aa to unsigned int to output the numeric value, since ostream& operator<<(ostream&, … Read more