Still seems to be the case with current git - tested with swig -c++ -xml Examples/test-suite/class_ignore.i and looking for Foo in the output shows the class Foo isn't ignored.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
XML isn't really a target language at all and it never will be! It's not much different to the -debug-top debug option which dumps internal parse tree information. The main difference is the format of the output.
The Foo class appears in the output of swig -c++ -python -debug-top 1 Examples/test-suite/class_ignore.i (and similarly for -debug-top 2 to -debug-top 4) .
So while -xml is essentially undocumented, I think this is working as intended - i.e. it's dumping out the parse tree, and class Foo exists in the parse tree. Closing as not-a-bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Still seems to be the case with current git - tested with
swig -c++ -xml Examples/test-suite/class_ignore.iand looking forFooin the output shows the classFooisn't ignored.In https://github.com/swig/swig/issues/2213 @wsfulton said about
-xml:The
Fooclass appears in the output ofswig -c++ -python -debug-top 1 Examples/test-suite/class_ignore.i(and similarly for-debug-top 2to-debug-top 4) .So while
-xmlis essentially undocumented, I think this is working as intended - i.e. it's dumping out the parse tree, and classFooexists in the parse tree. Closing as not-a-bug.