Skip to content
New issue

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

Compound types in enums are unsupported (from @vit9696) #11

Open
d0c-s4vage opened this issue Sep 11, 2016 · 0 comments
Open

Compound types in enums are unsupported (from @vit9696) #11

d0c-s4vage opened this issue Sep 11, 2016 · 0 comments
Assignees
Labels

Comments

@d0c-s4vage
Copy link
Owner

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
};
@d0c-s4vage d0c-s4vage added the bug label Sep 11, 2016
@d0c-s4vage d0c-s4vage self-assigned this Sep 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant