On 10/8/2021 8:38 AM, Nikolay Sivov wrote:
I think you could simply implement test handler objects that support both interfaces, and switch between them using some flag.
It looks like which content handler is used (SAX... or VBSAX...) depends on which interface the reader parse call is made through (ISAXXMLReader_parse or IVBSAXXMLReader_parse). So a flag can be used to switch between these reader interfaces, however each needs the correct content handler assigned to it.
Is that necessary? Support data is meant for version-specific classes. For SAXReader, it's never a situation when you can create C++ interface, and not VB interface.
Turns out it's not necessary. I'm not sure why, but during testing I thought I needed to get support for VB interfaces as well.