3 ms·
It's 0x20 like others pointed out. The wrapping rule here is that signed integer overflow is UB.
by juunpp 3y ago
It's 0x20 like others pointed out.
The wrapping rule here is that signed integer overflow is UB.
- defrost 3y agoAssuming ASCII char encoding ... which isn't a given in C, just extremely commonplace.
- ryao 3y agoThe ascii numbers being assigned to characters is a famous example of one C compiler passing on knowledge to a compiler it builds without ever having it specified in the source code. Given that, I am surprised to hear it ever is anything different.
- defrost 3y agoEBCDIC persisted later than many might expect - to 1990 in legacy hardened IBM System/360's used in air traffic and defence (branded as IBM 9020's IIRC). Early C compiler projects (eg: The Hendrix Small-C of ~1982) would get patched by some to support the full C language and extended to cross compile to and from whatever machines were about at the time, System/360's, VAX, PDP's, early PC's, BBC micros, etc. It wasn't always the case that char encoding passed on by default, there was always the option to insert a trans table whether compiling or dealing with data stored in not native form (similar to data in big end V little end).