João Matos
João Matos
I haven't been using Windows for CppSharp development for a bit, and yes it's easy to fix.
> @tritao Do you think we should refactor the `Parser.cpp` to remove `TypeLoc` usage. If possible yes, it would simplify the parser code a bit. > Why do the current...
> BTW I am having trouble parsing a relatively big project (without any processing, just parsing and AST generation), with around 650 header files, the process is crashing out of...
Since it parses all the headers as a single translation unit, it can be significantly faster than parsing header by header, at the cost of a bit more memory usage.
I would try to understand what's going on with that particular project, it must be generating a ton of unnecessary garbage. First figure out how much memory parsing with Clang...
Cool, I actually developed a prototype C# binding for Urho3D with CppSharp many years ago, so it was definitely parseable back then. Also @rokups (from rbfx) contributed a few fixes...
Maybe https://github.com/mono/CppSharp/blob/main/src/Generator/Passes/HandleDefaultParamValuesPass.cs?
Nice debugging, that sounds like an annoying issue. So should I merge this one right away, assuming we fix this new C++17 issue at a later stage?
Hey mate, how is progress, still working on this?