Closed Stunkymonkey closed 1 year ago
I'm very time constrained currently. Please suggest a fix and I'll be happy to merge. I suspect that the issue is that I specified the enum's type - if you can work out places that rely on that (sizeof?) and fix it there too, then that could work.
On another note, I didn't know that there's a package, that's really cool 😎
my current fix is patching it to 255
which is the maximum of the char
. Not sure if that is a good idea... maybe @andro2157 can say somthing about it? Since he is the one introducing the OUT_OF_RANGE
variable.
That's interesting. I copied the enums from the official Sony app apk. The OUT_OF_RANGE
variable is defined like this :
OUT_OF_RANGE((byte) -1);
The byte
type in java is an equivalent for the signed char
in C++. I guess that here there's an ambiguity about the use of the char
type. I used it as an implicit signed char
, so changing the char
type to a signed char
would be a proper fix I guess ?
If the char
type is interpreted as a signed char
, I guess that 255
might cause a cast warning on some compilation settings.
so you suggest having something like?:
enum class VPT_INQUIRED_TYPE : signed char {
Just assuming this here: https://en.wikipedia.org/wiki/C%2B%2B11#Strongly_typed_enumerations This kind of fix would be easy.
Yep exactly!
I am the package-maintainer of the nix-package. But currently it does not build on aarch64 out of the box. I am currently getting this issue:
for version
1.2
I did remove the line containingUNKNOWN = -1
. For the newer versionOUT_OF_RANGE
appeard as well. So I am suggesting in fixing this bug upstream, then patching it all the times.I would be happy to have a proper fix. Maybe setting it to the maximum would result in the same behavior?