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 #24

Closed
vit9696 opened this issue Oct 26, 2015 · 1 comment
Closed

Compound types in enums are unsupported #24

vit9696 opened this issue Oct 26, 2015 · 1 comment
Labels
Milestone

Comments

@vit9696
Copy link

vit9696 commented Oct 26, 2015

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 bug and removed bug labels Sep 10, 2016
@d0c-s4vage d0c-s4vage modified the milestone: 0.2 Sep 10, 2016
@d0c-s4vage
Copy link
Owner

This is a py010parser error - closing here and recreating in that project.

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

2 participants