In the book \"Complete Reference of C\" it is mentioned that char
is by default unsigned.
But I am trying to verify this with GCC as well as Visual Stud
According to "The C++ Programming Language" by Bjarne Stroustrup, char
is "implementation defined". It can be signed char
or unsigned char
depending on implementation. You can check whether char
is signed or not by using std::numeric_limits<char>::is_signed
.
The book is wrong. The standard does not specify if plain char
is signed or unsigned.
In fact, the standard defines three distinct types: char
, signed char
, and unsigned char
. If you #include <limits.h>
and then look at CHAR_MIN
, you can find out if plain char
is signed
or unsigned
(if CHAR_MIN
is less than 0 or equal to 0), but even then, the three types are distinct as far as the standard is concerned.
Do note that char
is special in this way. If you declare a variable as int
it is 100% equivalent to declaring it as signed int
. This is always true for all compilers and architectures.
According to The C Programming Language book by Dennis Ritchie which is the de-facto standard book for ANSI C, plain chars either signed or unsigned are machine dependent, but printable characters are always positive.
As Alok points out, the standard leaves that up to the implementation.
For gcc, the default is signed, but you can modify that with -funsigned-char. note: for gcc in Android NDK, the default is unsigned. You can also explicitly ask for signed characters with -fsigned-char.
On MSVC, the default is signed but you can modify that with /J.
Now, we known the standard leaves that up to the implementation.
But how to check a type is signed
or unsigned
, such as char
?
I wrote a macro to do this:
#define IS_UNSIGNED(t) ((t)~1 > 0)
and test it with gcc
, clang
, and cl
. But I do not sure it's always safe for other cases.
C99 N1256 draft 6.2.5/15 "Types" has this to say about the signed-ness of type char
:
The implementation shall define char to have the same range, representation, and behavior as either signed char or unsigned char.
and in a footnote:
CHAR_MIN
, defined in<limits.h>
, will have one of the values0
orSCHAR_MIN
, and this can be used to distinguish the two options. Irrespective of the choice made,char
is a separate type from the other two and is not compatible with either.