Re: New VSI post on Youtube

On 8/14/24 19:48, Arne Vajhøj wrote:

On 8/14/2024 2:33 PM, Arne Vajhøj wrote:

And it has different size of long and pointers. Causing problems
for two cases:
* code that make implicit assumptions that those are 32 bit
* mixing C and C++

 I am getting more and more convinced that C and C++
code should completely switch to the explicit length
model.
 So:
 #include <stdint.h>
 or:
 #include <cstdint>
 and use:
 int8_t
int16_t
int32_t
int64_t
uint8_t
uint16_t
uint32_t
uint64_t
 and consider putting:
 #define int ">>>> DO NOT USE INT <<<<"
#define short ">>>> DO NOT USE SHORT <<<<"
#define long ">>>> DO NOT USE LONG <<<<"
 in as well to enforce.
 Where did I put that asbestos suit to protect me
from the C/C++ crowd?
 :-)
 Arne
>

For years in embedded work here, there is always a header file, wordsize.h which aliases such as U8, U16, U32 etc, to the bit
sizes of the types related to the cpu variant and tools in
use. Pretty foolproof, and important for embedded work, where
you often need to know the width of hardware registers, and
the variables and pointers that interact with them...