typedef signed char int8_t; typedef signed short int int16_t; typedef signed int int32_t; typedef signed __int64 int64_t; ...
passing a variable defined as uint8_t to a standard library function gives warnings. this has resulted to a lot of warnings in the code.
This can be a worrisome situation for the colleague who may refer to the code.
is there any way in which the toolchain knows that both definitions are one and the same and that warnings must not be generated?
View all questions in Keil forum