Check type selection for sizes
I think it is good. Do you have an idea for list up the points of replace?
I'm sorry - I do not really understand your reply on this issue.
I have pointed already to places in the source files which might need further clarification on better data type selection.
I'm grateful for your suggestion, but I guess your meaning isn't correct only the "Example" points.
Do you have any idea for find *all of the place* that need to change data type?
I do not know the source files good enough to definitely say in all places where negative values are really acceptable for integral data types. I have got the impression that there are still more update candidates in the source code where unsigned types will improve software correctness.
I hope to get a clarification on the interface design from the core software developers.
Disputed points and side-effect are too many, and team members doesn't have enough time to fix this issue.
How can the concerns about potential side effects be clarified?
How do you think about to replace any "int" and "long" for parameters like "pos", "len" or "destlen" by the data type "size_t"?
Examples: