Alexandre Mutel

> Is there any specific reason this has to be internal ? Especially given the plugin architecture ? I think that's probably ok to make it public. I recently fixed...

> I'm not entirely sure what the result of this should look like, but probably a calculated value for the enum? It should print the characters, don't know why it...

you mean [this](https://github.com/xoofx/CppAst.CodeGen/blob/e28771df6cef483bffd9cf6bec34c70880ec773b/src/CppAst.CodeGen/CSharp/Plugins/DefaultEnumItemConverter.cs#L27-L43)?

https://github.com/xoofx/CppAst/blob/b27338c68fae3ab189ad58573b27a7e3547f98a9/src/CppAst/CppModelBuilder.cs#L192-L205

This one should be easy to fix as well.

Yes, unfortunately, I'm not sure if we have any workaround for this. The problem is that libclamg-C does not parse or give access to these attributes correctly, so we need...

Correct, ParseAsCpp is doing this: https://github.com/xoofx/CppAst.NET/blob/f2d7445e2d81d7eebc559a7f4284ec8a5967cd44/src/CppAst/CppParser.cs#L97-L100 But you can pass other arguments to clang directly.

Are you checking/outputing that the result of parsing doesn't have any error or messages? (e.g `compilation.Diagnostics.HasErrors` and `compilation.Diagnostics.Messages`)

Definitely possible, as attributes have to be parsed manually, so there might be some bugs.

Yep likely