On Thursday, 15 September 2022 12:20:37 PDT samuel ammonius wrote: > It's really hard to imagine what SWIG's output looks like without seeing it > for > yourself, so I'll just post one of the outputs here. This was the shortest, > most > readable, and most C/C++ compatible output I could get from all the target > languages available in SWIG. > > pastebin link <https://pastebin.com/gfkj6Bug> > > I think it makes a bit more sense now why it would probably be harder to > wrap SWIG's output than to wrap C++ directly.
Even though that code has #ifdef __cplusplus, the code doesn't compile as C. This is C++. The question is what the C API would look like, in a header compileable as C. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
