220 - typedef uint32_t ValueType;
221 + typedef int ValueType;
(and related uint_32 -> int changes)
While these changes fix the problem mentioned here, I imagine that there was a reason for choosing uint32_t, and that this change could have unintended consequences. Has this been checked?
220 - typedef uint32_t ValueType;
221 + typedef int ValueType;
(and related uint_32 -> int changes)
While these changes fix the problem mentioned here, I imagine that there was a reason for choosing uint32_t, and that this change could have unintended consequences. Has this been checked?