Valueless enum members are generated incorrectly

[natezb]

This seems to have been introduced by #216, which inadvertently removed some special-case checks. Enum members that don't have an assigned value now generate an invalid, empty assignment. For example:

typedef enum MOT_TravelModes
{
  MOT_TravelModeUndefined = ,
  MOT_Linear = 0x01,
  MOT_Rotational = 0x02
} MOT_TravelModes;

In the original code, MOT_TravelModeUndefined was assigned no value, and should be generated with no = sign.

[SethPoulsen]

I just came here to report them same problem. I'm going to have a go at fixing it.

[eliben]

@altendky PTAL

[SethPoulsen]

No need. I got it sorted out.

[saullocarvalho]

Is this still an issue? It seems like a commit has already fixed it.

[SethPoulsen]

Ya, I fixed it. It should be closed.

[natezb]

Just tested under 2.19, and works for me.