We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
courtesy of @vit9696 at d0c-s4vage/pfp#24:
Multiword types like "unsigned short" or "unsigned char" are causing a parse error when used in enum declarations. E. g.
enum <unsigned short> MY_ENUM { VAL_1 = 0, VAL_2 = 1 };
If one creates a typedef and replaces the type by a single word, it will be ok. I. e.
typedef unsigned short u16; enum <u16> MY_ENUM { VAL_1 = 0, VAL_2 = 1 };
The text was updated successfully, but these errors were encountered:
d0c-s4vage
No branches or pull requests
courtesy of @vit9696 at d0c-s4vage/pfp#24:
Multiword types like "unsigned short" or "unsigned char" are causing a parse error when used in enum declarations. E. g.
If one creates a typedef and replaces the type by a single word, it will be ok. I. e.
The text was updated successfully, but these errors were encountered: