ISO C states what the differences are. The int data type is signed and has a minimum range of at least -32767 through 32767 inclusive. The actual values are given in limits.h as INT_MIN and INT_MAX respectively. An unsigned int has a minimal range of 0 through 65535 inclusive with the actual maximum value being … Read more
Your last approach seems promising. You can improve on that by manually considering the lowest bits of a and b: unsigned int average = (a / 2) + (b / 2) + (a & b & 1); This gives the correct results in case both a and b are odd.
Py_ssize_t is signed. See PEP 353, where it says “A new type Py_ssize_t is introduced, which has the same size as the compiler’s size_t type, but is signed. It will be a typedef for ssize_t where available.” You should use Py_ssize_t for indexing. I didn’t find a definitive statement of this in the Cython docs, … Read more
In the first two cases, you simply forgot to actually call the member function (!, it’s not a value) std::vector<int>::size like this: #include <vector> int main () { std::vector<int> v; auto size = v.size(); } Your third call int size = v.size(); triggers a warning, as not every return value of that function (usually a … Read more
int value can be -2147483648 these are 11 digits so the default display size is 11 unsigned int does not allow negative numbers so by default it need only display size 10 As the documentation below shows, the number of bits required to store SIGNED INT and UNSIGNED INT is the same, the range of … Read more
One possible aspect is that unsigned integers can lead to somewhat hard-to-spot problems in loops, because the underflow leads to large numbers. I cannot count (even with an unsigned integer!) how many times I made a variant of this bug for(size_t i = foo.size(); i >= 0; –i) … Note that, by definition, i >= … Read more
size_t is unsigned for historical reasons. On an architecture with 16 bit pointers, such as the “small” model DOS programming, it would be impractical to limit strings to 32 KB. For this reason, the C standard requires (via required ranges) ptrdiff_t, the signed counterpart to size_t and the result type of pointer difference, to be … Read more
As you are probably aware, ints are stored internally in binary. Typically an int contains 32 bits, but in some environments might contain 16 or 64 bits (or even a different number, usually but not necessarily a power of two). But for this example, let’s look at 4-bit integers. Tiny, but useful for illustration purposes. … Read more
It is usually a good idea to declare variables as unsigned or size_t if they will be compared to sizes, to avoid this issue. Whenever possible, use the exact type you will be comparing against (for example, use std::string::size_type when comparing with a std::string‘s length). Compilers give warnings about comparing signed and unsigned types because … Read more