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

Bug with enum bitfield in struct (Origin: bugzilla #313527) #1770

doxygen opened this Issue Jul 1, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 1, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.4.x on platform Other
Assigned to: Dimitri van Heesch

On 2005-08-15 15:05:56 +0000, Jan Eyolf Bjørnsen wrote:

Please describe the problem:
Doxygen ignores enum bitfields in struct:

struct test{
enum cause_error:2; /< Two bit enum */
unsigned char blabla:1; /
< 1 bit value */


Data Fields
unsigned char blabla:1

Field Documentation
unsigned char test::blabla
< Two bit enum 1 bit value

This code is accepted without warnings in CodeVision AVR compiler

Steps to reproduce:
Described above

Actual results:
Described above

Expected results:
I would expect the enum value to be included under "Data Fields" and in "Field

Does this happen every time?

Other information:

On 2005-08-15 15:10:24 +0000, Jan Eyolf Bjørnsen wrote:

The struct example should be

struct test{
enum cause_error test_enum:2; /< Two bit enum */
unsigned char blabla:1; /
< 1 bit value */

On 2010-10-13 10:08:19 +0000, Peter wrote:

Any news about this issue?
Still present in version 1.7.2.

On 2010-10-16 13:24:10 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-01-03 19:01:44 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 1, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment