所以我想要一个整型数。
我想要一个整型数，一个冒号，和一个，使其更美观的空格。
I'd like an integer please, a colon, and a space just for aesthetic reasons.
这个问题只会发生在,当你用一个整型数除以一个整型数的时候。
The problem only arises if you have an int divided by an int.
一个整型数的地址，但是在函数，大括号中的环境中，意思是定位到那个地址。
Expect the address of an int but here in the context of the function itself inside the curly braces, it means go to that address.
所以即使那个正确的答案是4，或别的数值，当你用一个整型数除以一个整型数，在那个变量的返回值里，只有，存储一个整型数的空间。
So even if the correct mathematical answer is 1.4 or whatever, when you divide an int by an int, you only have room in that variable, in the response for an actual integer.
一些处理器在处理无符号整型数要比处理符号整型数快得多，这也是一个好的习惯，有利于代码的自我文档化(self- documenting)。
Some processors can handle unsigned integer arithmetic considerably faster than signed (this is also good practice, and helps make for self-documenting code).
比如，如果出于优选的考虑，您希望适应性是一个7位的整型数，您想要的范围就是0到32767之间。
You may want a range between 0 and 32767, for instance, if you want the fitness to be a 7-bit integer for optimization.
它直接把小数点后面的数值丢弃掉了，因为，凭直觉，那些整型数和结果应该是一个浮点数据，但是我需要一个更精确的数值。
It just throws the decimal point away and that's because, again, these are ints and the answer intuitively should be a floating point value, but I need to be more specific.
所以我可以通过改变其中一个，整型数为浮点数。
And I can fix this just by changing one of those values to a floating point.
我们知道从周三起--简单说下-,我们有个叫做“char“或“char“,看你们怎么读它了，那代表一个单一的字符,但那里会有个整型数与之对应。
We know from Wednesday if -- briefly -- that there's this thing called a "char" or "char," depending on how you want to pronounce it, which is just a single character but where there's also an int.
我们知道从周三起--简单说下-,我们有个叫做“char“或“char“,看你们怎么读它了，那代表一个单一的字符,但那里会有个整型数与之对应。
We know from Wednesday if -- briefly -- that there's this thing called a "char" or "char," depending on how you want to pronounce it, which is just a single character but where there's also an int.
应用推荐