Should I use "unsigned" every time i know I'm processing unsigned values?

Question

Often values are known to be positive. For example TCP/UDP sequence number is always positive value. Both int and unsigned int are big enough to store even the biggest sequence number so I can use any of these types. There are many other examples when values are known to be positive.

Are there any reasons to use unsigned type when capacity of regular signed type is enough (and often more than enough)?

Personally I tend to use regular types because:

int is probably a little bit more readable than uint or unsigned int
I don't need to include extra headers for UINT etc.
I will avoid extra casts somewhere further in the program

Reasons to use unsigned type I can imagine:

help compiler generated better code?
help another programmer to understand that variable is unsigned
avoid possible bugs (for example when int is assigned to UINT compiler likely will generate compile-time error and we should check that value we assign is not negative)

Some thoughts about it here: embeddedgurus.com/stack-overflow/2009/08/… — Morwenn
– Morwenn, Commented Apr 24, 2013 at 9:36
thanks, also I've found that question just now stackoverflow.com/questions/12225521/… — Oleg Vazhnev
– Oleg Vazhnev, Commented Apr 24, 2013 at 9:38
No. There are some arguments against using unsigned - Stroustrup alludes to this in passing in The C++ Programming Language somewhere - Lakos went off and wrote a chapter about it in one of his books: tedious. Example issues: if you have values a and b, abs(a - b) tends to work intuitively for ints but not unsigned; and it's noteworthy that Standard conversions can kick in silently so the kind of checks you might hope to get from using unsigned don't work anyway - negative values become silently huge and vice versa. — Tony Delroy
– Tony Delroy, Commented Apr 24, 2013 at 9:39
Mixing signed and unsigned is an important source of bugs. I would stick to signed in all but specialist situations. — john
– john, Commented Apr 24, 2013 at 9:40

Community · Accepted Answer · 2017-05-23 11:43:18Z

1

One reason is that comparing signed and unsigned numbers can lead to surprising results. In C and (I think) C++, comparing signed and unsigned numbers causes the signed number to be interpreted as unsigned. If the signed value happens to be negative, reading it as unsigned will give a LARGER value than any unsigned number, which is not what you want. See this question for an example in Objective-C, which uses the same conversion rules as C.

edited May 23, 2017 at 11:43

CommunityBot

11 silver badge

answered Apr 24, 2013 at 9:49

Caleb

125k19 gold badges189 silver badges282 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Should I use "unsigned" every time i know I'm processing unsigned values?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related