Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Per the SWIG Documentation (21.9.1 Default primitive type mappings), the C uint8_t is mapped to a Java short which is 16 bits and the C uint_15_t is mapped to a Java int which is 32 bits. I believe the C functions are 8 and 16 bits respectively, why does SWIG double the number of bits when wrapping in Java?
The problem is that Java types are always signed.
Thus if you have an unsigned C type that goes from 0 to 255, the smallest Java type that can represent the upper half of that range is a short.
The alternative is that you shift or somehow transform your
uint8_tto use the negative parts of Java’sbyte, but the semantics of that are very counterintuitive.