Check type selection for sizes

[elfring]

I guess that a few functions will not work correctly if they will get negative values.
How do you think about to replace any "int" parameter like "length" by the data type "size_t"?

[farindk]

No, that just hides errors and there is no reason to save this one bit. If some computation gives negative values, errors are obvious. If you use unsigned, they overflow and are more difficult to find.

[elfring]

I am surprised that you do not like unsigned integers here. I would prefer their use at various places to make the software a bit safer by design.

[farindk]

Feel free to do so.
And then have fun with code like

for (uint32_t i=length-1;i>=0;i--) { ... }

2013/9/6 Markus Elfring notifications@github.com

I am surprised that you do not like unsigned integers here. I would prefer
their use at various places to make the software a bit safer by design.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-23928788
.

[elfring]

for (uint32_t i = length - 1; i >= 0; --i) { ... }

Would you like to point out that the data types "uint32_t" and "size_t" have got different value ranges eventually?