Re:Pitfalls in C and C++: Unsigned Types (2011)
by Mindless2112 on Wednesday September 25, 2013 @02:32PM
(#6446387)
> “Unsigned has a bigger range.”
> Only a bit bigger.
So... "only" twice as big.
I'm not particularly fond of the trend toward avoiding unsigned integers (in particular the lack of unsigned types in Java and array lengths being signed in C#).
A good programmer should be capable of determining whether to use a signed or unsigned type; if it's not easy to decide, that indicates a design flaw to me.
I'm not particularly fond of the trend toward avoiding unsigned integers (in particular the lack of unsigned types in Java and array lengths being signed in C#).
A good programmer should be capable of determining whether to use a signed or unsigned type; if it's not easy to decide, that indicates a design flaw to me.