Many first-time programmers rush over variable type descriptions and head full-bore into coding. That’s fine. I did it. You probably did it. But eventually you encounter code that doesn’t work properly because of negative numbers. That’s when you go back and review the concept of negative integer variable types.
\n
\nUnlike floating point numbers, integers are stored in memory using plain old binary. If you can read binary (or hex), you can look at a clutch of bits and quickly divine what the value could be. In fact, nerds pride themselves on such abilities:<\/p>\n
The int<\/em> variables you create in C are signed unless you specify the unsigned<\/em> type. That means those variables can store both positive and negative values. A signed<\/em> keyword exists to assert that fact, but it’s redundant for plain int<\/em>, char<\/em>, long<\/em>, short<\/em>, and long long<\/em> variables.<\/p>\n This issue with signed variables is that at a certain point, large values become negative. This effect can get your code into trouble if you’re unaware of negative binary numbers.<\/p>\n Unlike reading positive binary numbers, reading a negative binary value isn’t something most nerds can do:<\/p>\n The far left bit in a signed integer value is the sign bit. When set, it determines that the value stored is negative. That bit doesn’t work like the minus sign in decimal math. The value above isn’t -3, it’s -32765. In fact, -3 looks like this when stored in a short signed int<\/em> variable:<\/p>\n That representation might make no sense until you understand how binary values are counted and what happens when the bits keep flipping in the same direction.<\/p>\n In the following program, char<\/em> variable Here is a snippet of the output:<\/p>\n If you modify the code, and edit Line 5 to read:<\/p>\n Then the output looks like this (snippet):<\/p>\n The program stops at 255 because at that point, all the bits in the value flip back to zero.<\/p>\n The same binary values are used in both programs, but when the integer variable is signed<\/em>, the output shows negative numbers.<\/p>\n The signed int<\/em> and unsigned int<\/em> values also explains why the range of integer numbers is show in two sets. Refer to Appendix D in Beginning C Programming For Dummies<\/em> to view the values and ranges.<\/p>\n In next week’s Lesson<\/a>, I explore further the concept of negative Integers and how they work.<\/p>\n","protected":false},"excerpt":{"rendered":" How negative values are stored in integers. Continue reading 0110 0101 1110 0001 = 0x65E1 = 26081<\/code><\/p>\n1000 0000 0000 0011 = 0x8003 = -32765<\/code><\/p>\n1111 1111 1111 1101 = 0xFFFD = -3<\/code><\/p>\nz<\/code> is signed. It starts at 1 and loops “up” to zero. It does this because after positive value 127, the signed char<\/em> variable z<\/code> sets its far left bit to 1, making the values negative. The next value after 127 is -128, which then steps up to zero:<\/p>\n\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n char z;\r\n\r\n z = 1;\r\n while(z != 0)\r\n {\r\n printf(\"%d\\n\",z);\r\n z++;\r\n }\r\n\r\n return(0);\r\n}<\/pre>\n1\r\n2\r\n3\r\n4\r\n...\r\n126\r\n127\r\n-128\r\n-127\r\n...\r\n-4\r\n-3\r\n-2\r\n-1<\/code><\/pre>\nunsigned char z<\/code><\/pre>\n1\r\n2\r\n3\r\n4\r\n...\r\n252\r\n253\r\n254\r\n255<\/code><\/pre>\n