You are on page 1of 4

Signed and unsigned int An int can store negative numbers that usually range from about -2.

1 billion to about 2.1 billion. An unsigned int can only store positive numbers that usually range from 0 to about 4.2 billion. In a 32-bit system, an int is typically 32-bits long with the first bit being the "sign bit". If the sign bit is "set", the number is considered negative. If you have an unsigned, the "sign bit" is ignored and is just considered another bit in the number. 1. sign bit 2. | 3. V 4. 0000 0000 0000 0000 0000 0000 0000 0000 5. | 6. V 7. 1111 1111 1111 1111 1111 1111 1111 1111
int with a value of -1 //on most systems, this represents an //this always represents zero (0)

8. X 9. 10. 1111 1111 1111 1111 1111 1111 1111 1111
4,294,967,296 (about 4.2 billion) //in an unsigned int, this represents

Q2 signed and unsigned char
Question As when I compile: ----------#include <iostream> using namespace std; int main() { char ch1 ='Ç'; unsigned char ch2 ='Ç'; cout<<ch1<<"\t"<<ch2 <<endl; cout<<ch1+0<<"\t"<<ch2+0 <<endl; char ch3 =128; cout<<ch3; return 0; }

To get the magnitude (i. The reason you get the characters for the lines: cout<<ch1<<"\t"<<ch2 and: cout<<ch3. In my locale using a console (CMD. (This information came from the hint text that appears when you hover over a character in the MS Windows character map application: the text read: U+00C7: Latin Capital Letter C With Cedilla 199 represented as an 8-bit 2s complement signed value is -57: 199 == 1100 0111 binary. . First the character you chose from the Windows character map is obviously not the same as that with character code 128 (0x80) in fact when I check it on my system it says it has a value of 0xC7 = 192 + 7 = 199. On the other hand you get the values of the characters with the line: . .. the positive equivalent) we flip the bits (1s complement) and add 1 (2s complement): 0011 1000 + 1 = 0011 1001 = 0x39 = 57 Thus the bit pattern 1100 0111 represents an 8-bit unsigned value of 199 or a signed 8-bit 2s complement value of -57.. I would expect something similar to happen to my A-with tilde characters shown above when I post this answer text back to you.EXE) under Windows Vista the output is: Ã -57 Ç Ã 199 (Those are A with tilde characters on the first line) I am not sure where the ╟ ╟ comes from in your output but suspect it is due to translation of the question text through AllExperts.Output: ╟╟ -57 199 ÇPress any key to continue .e. The top bit is 1 so if the value is signed it will be negative. is that you are passing char values to the cout ostream which just passes the value to the console for display as a character.

and once you have products interpreting char as signed and others interpreting char as unsigned getting one side to change is an uphill struggle as all code written for those compilers will assume signed (or unsigned) char by default. but then the compiler will complain when you try to build the program! Now onto the char types. The reason for this is probably historic. Whether a plain char type is signed or unsigned depends on the compiler (and quite possibly the compiler flags .cout<<ch1+0<<"\t"<<ch2+0 because adding a literal zero adds an int value. Also if doing manipulations on character codes . This is also why compilers often have options to override their preferred default signedness for char to help when porting code from a system/compiler that defaults to the alternate signedness for char. 127+72=199. but if signed would be -57. and of course the keyboard.at least not as far as I can tell and I recently had occasion to try! On the other hand the value 128 does appear to be the character you were originally after in the console codepage used on both our systems by default.gcc has the -fsigned-char funsigned-char options and MS VC++ has the /J . the Visual Studio editor which does accept UNICODE characters . It is how the bit pattern is interpreted when performing arithmetic . This encoding can handle over a million character codes .and no I do not like it much either! Windows in the main uses UNICODE encoding (UTF16) internally.set default char to unsigned option). Remember that what value produces what character is a matter of mappings and fonts in use at the time.adding an offset to a signed char will probably not get the expected result (although the bit pattern may be correct. there are in fact three types for char: char. and these may well differ between applications such as consoles and GUI based editors.65536 in a single 16-bit value and the rest using special 2 16 bit character sequences. The editor will accept the fancy quote characters used by Word.a good way us to quote something in MS Word and copy and paste the quoted text including the quotes to a program in a Visual Studio edit window.it is often useful to modify bit patterns and add offsets and the like .try it in main code and see .the other use for char is as a small integer rather than a character.the multi-byte 8-bit encoding for UNICODE characters . Int values sent to ostreams are formatted as a sequence of digit characters that represent the integer's value. The difference between signed and unsigned char is the same as the difference between signed and unsigned versions of the other integer types. e. and char is commonly of byte size. any tests may fail e. The console however is resolutely 8-bit character based with the upper 128 characters being determined by the choice of the code page (see the chcp command). Unlike other integer types char does not automatically indicate a signed character. If tested for say > 32 the test will fail). Many I/O devices use byte sized registers for example. thus the result of the expressions ch1+0 and ch2+0 are int not a char values.for example when converting from one character encoding scheme to another . I am not sure exactly what you mean by having two values .g. Another area of confusion with signed values is right shifting as the sign bit is often . Thus a change one way or the other is likely to break people's code .if you mean that bit patterns can be interpreted in different ways then yes. It cannot even handle UTF-8 .g.and there is a lot of old C and C++ code out there. other than the fact that to ensure you get a signed char you have to state signed char and not just char as noted above. You could also convert them explicitly to ints: cout<<int(ch1)<<"\t"<<int(ch2) The reason the character output is different in the console to the main Windows environment is that the code page used differs . signed char and unsigned char.

Exactly how signed types are represented is up to the compiler/system. If E1 has an unsigned type or if E1 has a signed type and a nonnegative value. ." So it is usually best to view the values as definitely unsigned in such cases. the value of the result is the integral part of the quotient of E1 divided by the quantity 2 raised to the power E2. but may not be (logical shift) as the standard says: "The value of E1 >> E2 is E1 right shifted E2 bit positions. the resulting value is implementation defined.extended down the shifted bits (sign extended/arithmetic shift). as noted at the beginning of the answer. Another alternative would be sign magnitude representation in which the highest bit just indicates + or . sign. The most common on desktop systems is of course 2s complement. Thus in sign magnitude representation -57 and +57 differ only in the value of the top. If E1 has a signed type and a negative value.and the other bits are always just a binary representation of how positive or negative. bit.