Also, the unicode situation is troubling: your app is no longer fully accessible if it assumes a character is a char, as a character may be stored in two chars. As a char is internally stored and manipulated as an int, it might have been better (albeit very heavy handed) to make a char an unsigned int. Backwards compatibility could be maintained in almost all situations (you shouldn’t be doing arithmetic with a char anyway…).