As pointed out by Anders Forsgren, there is no unsigned doubles in the IEEE spec (and therefore not in C#). You can always get the positive value by calling Math.Abs() and you could wrap a double in a struct and enforce the constraint there: public struct PositiveDouble { private double _value; public PositiveDouble() {} public … Read more
ssize_t is used for functions whose return value could either be a valid size, or a negative value to indicate an error. It is guaranteed to be able to store values at least in the range [-1, SSIZE_MAX] (SSIZE_MAX is system-dependent). So you should use size_t whenever you mean to return a size in bytes, … Read more
Because the int value is promoted to an unsigned int. specifically 0xFFFFFFFC on a 32-bit machine, which as an unsigned int is 4294967292, considerably larger than 10 C99 6.3.1.1-p2 If an int can represent all values of the original type (as restricted by the width, for a bit-field), the value is converted to an int; … Read more
They are the same type, as in C. No differences at all. Of course, unsigned can be used as a qualifier for other integral types. But by default, unsigned is the same as unsigned int.
unsigned is a modifier which can apply to any integral type (char, short, int, long, etc.) but on its own it is identical to unsigned int.
std::string sName(reinterpret_cast<char*>(name)); reinterpret_cast<char*>(name) casts from unsigned char* to char* in an unsafe way but that’s the one which should be used here. Then you call the ordinary constructor of std::string. You could also do it C-style (not recommended): std::string sName((char*) name);
document.write( (1 << 31) +”<br/>”); The << operator is defined as working on signed 32-bit integers (converted from the native Number storage of double-precision float). So 1<<31 must result in a negative number. The only JavaScript operator that works using unsigned 32-bit integers is >>>. You can exploit this to convert a signed-integer-in-Number you’ve been … Read more
Using int is more correct from a logical point of view for indexing an array. unsigned semantic in C and C++ doesn’t really mean “not negative” but it’s more like “bitmask” or “modulo integer”. To understand why unsigned is not a good type for a “non-negative” number please consider these totally absurd statements: Adding a … Read more
Just using int everywhere may seem tempting, since it minimizes the need for casting, but there are several potential pitfalls you should be aware of: An int might be shorter than you expect. Even though, on most desktop platforms, an int is typically 32 bits, the C standard only guarantees a minimum length of 16 … Read more
There is no concept of signedness for bool. From [basic.fundamental]/6: Values of type bool are either true of false. [Note: There are no signed, unsigned, short, or long bool types or values. — end note] Values of type bool participate in integral promotions (4.5). By contrast, signedness is explicitly called out for the signed integer … Read more