[xsd-users] Issue with XSD 4.2.0 - DOMDocument explicit namespacing

[Harry Grace]

> Thanks for the report. I've fixed it a bit differently so if you could
> try the patch and confirm it works for you, that would be great:

Hi Boris,

Yes, the patch works and I no longer experience the errors I was
originally receiving, thank you for the prompt response.

Will this patch be pushed out as an official release as perhaps a 4.2.1?
Also, does this require me rebuilding everything including the XSD binary,
or just using the new libxsd runtime library folder with the updated files
in it?

> Also, for my understanding, with which C++ compiler and version are
> you seeing these errors?

I was using Visual Studio 2017 15.3, with MSVC 14.11, which I believe uses
toolset v141,
and compiler version 19.11. I would experience the errors when using
precompiled
headers within Visual Studio's project settings /Yc /Yu.

On Tue, Nov 21, 2023 at 1:40 PM Boris Kolpackov <boris at codesynthesis.com>
wrote:

> Harry Grace <hwgrace18 at gmail.com> writes:
>
> > There seems to be some more using namespaces xercesc in the xml/dom txx
> > files which are causing conflicts when developing on Windows.
> >
> > Two in parsing-source.txx, lines:
> > 219   XSD_DOM_AUTO_PTR<DOMDocument> doc;
> > 362   XSD_DOM_AUTO_PTR<DOMDocument> doc;
> >
> > One in serialization-source.txx, line:
> > 274   XSD_DOM_AUTO_PTR<DOMDocument> doc (
> >
> > As noted in the older threads, some explicit xercesc:: namespacing would
> > resolve this issue.
>
> Thanks for the report. I've fixed it a bit differently so if you could
> try the patch and confirm it works for you, that would be great:
>
>
> https://git.codesynthesis.com/cgit/xsd/xsd/commit/?id=a821131cf17a43f55082a660cf323fa72c0aab40
>
> Also, for my understanding, with which C++ compiler and version are
> you seeing these errors?
>