4 ms·
I think you hit the nail on the head: the problem is education. Generally, a C programmer who took the time to understand integer types and their behaviour won'
by eliteraspberrie 12y ago
I think you hit the nail on the head: the problem is education. Generally, a C programmer who took the time to understand integer types and their behaviour won't make mistakes with either signed or unsigned types. But making unsigned types second class only reinforces bad habits (or what I consider bad).
- audunw 12y ago> But making unsigned types second class only reinforces bad habits (or what I consider bad). What do you mean by that? Don't you think that having to do "import unsigned" before they use unsigned types, make some people think twice? Don't you think a few people might think "Do I really understand this feature? Should I perhaps read the documentation for this module?"