This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11919] int vs. typedef int bar/signedness of chars
- From: "nathan at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Aug 2003 15:14:22 -0000
- Subject: [Bug c++/11919] int vs. typedef int bar/signedness of chars
- References: <20030814122446.11919.hans.utz@informatik.uni-ulm.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11919
------- Additional Comments From nathan at gcc dot gnu dot org 2003-08-14 15:14 -------
char, signed char and unsigned char are three distinct types. [3.9.1]/1
char will have the same underlying properties as one of the other two,
but it is still a distinct type.
you are right it is a bug, the typedef should not effect overload
resolution. the char->signed char is an integral conversion, char->int is
an integral promotion (so is preferred)