What’s the point of using integers when you could simply code programs using floating-point values all the time to always get the best results? The reason is a good one, but it takes some explaining.
\n
\nThe answer has to deal with storage and processing power. Integers take less processing power to manipulate. Floating point values take more processing power. But just as you could use a screwdriver to pound in a nail, it’s always best to use the proper tool for the job.<\/p>\n
As an example, consider an int<\/em> and a float<\/em> variable. According to the sizeof<\/em> operator, on my computer both variable types occupy four bytes of storage.<\/p>\n The four bytes of storage are just that as far as the computer is concerned. It’s how the bytes are read that’s important. Consider these declarations:<\/p>\n The value stored in variable (I’ve added the dashes and spaces above to make the four bytes readable.) That’s straightforward: Binary The value stored in variable If the hex value (Just because you’re curious, I had to use a debugger to view the binary representation of floating-point value 123.45.)<\/p>\n The integer value 486, on the other hand, is read and digested in one gulp. It’s easy for the processor to deal with So while you could code all the variables in your program as floating point, you’re just adding more overhead. With today’s fast processors you probably won’t see much speed impact, but the point is why add overhead when you don’t have to? Instead, code integer values as int<\/em>s and use floating-point variables only when necessary.<\/p>\n","protected":false},"excerpt":{"rendered":" The computer’s processor views integer values and floating point numbers different. It’s important to choose the right type when you code your programs. Continue reading int i = 486;
\nfloat f = 123.45;<\/code><\/p>\ni<\/code> is 486. Its binary representation is:<\/p>\n0000-0000 0000-0000 0000-0001 1110-0110<\/code> or 0x1e6<\/code><\/p>\n111100110<\/code> is hex 0x1e6<\/code>, which is decimal value 486<\/code>. Maybe not obvious to you, but easy for a computer.<\/p>\nf<\/code> is 123.45. Its binary representation is:<\/p>\n0110-0110 1110-0110 1111-0110 0100-0010<\/code> or 0x66e6f642<\/code><\/p>\n0x66e6f642<\/code> is read as decimal, it shows up as 1,726,412,354. (I added commas for readability.) That’s nowhere near 123.45, so the processor is doing some kind of sorcery to extrapolate the proper floating point value.<\/p>\nint<\/code> values because, in a way, integers are its native tongue. Floating point values require translation. Back in the old days, that duty was handled by a separate math co-processor. Today, the math processor is integrated into the main CPU, but it’s still used to efficiently deal with non-integer values.<\/p>\n