reserved identifier violation about sandboxie

[DavidXanatos]

At some point I guess a refactoring of the code would be in order, but I think that is not one of the things to be done first.

[elfring]

How do you think about to avoid that this software depends on undefined behaviour?

[DavidXanatos]

Why would you assume its relaying on undefined behavior?
From not adhering to a naming convention to undefined behavior is IMHO quite a long way.

[elfring]

Would you like to delete any underscores in affected identifiers?

[DavidXanatos]

mmh...

When I search for "typedef struct _" in the code I get almost 200 results and there the _ is followed by a Capital latter.

And this practice to typedef struct _MY_STRUCT {...} MY_STRUCT,*PMY_STRUCT; is extremely popular.

Apparently the majority of developers agreed to ignore that particular issue.

Look if that would be a few things to change that, I don't care if it makes you happy I would have done it. But its 185 struct definitions, and MSFT's own SDK's and WDK's do the exact same thing. That to me is also a standard violation by the letter, as those are imho not parts of the compiler but external frameworks.