On Monday, April 22, 2019, Jefferson Carpenter <jeffersoncarpenter2@gmail.com> wrote:
>
> Indeed, I was thinking that instead of calling write_output_buffer at all when the destination is a DOMDocument, the DOMDocument's createNode etc. functions would be called instead. Perhaps the mxwriter would need to hold a reference to an IXMLDOMNode for in-progress nodes whose attributes and child nodes are presently being assigned.
>
> Note that presently even though write_output_buffer is called when the destination is a DOMDocument, it now contains the code
>
> + else {
> + FIXME("unsupported destination type for writing %d\n", writer->dest_type);
> + }
>
> which would be called if the destination were set to a DOMDocument.
>
> It's not clear without tests whether the entire result is cloned back on endDocument, or whether the DOMDocument is built progressively in response to events sent to the SAXContentHandler.
>

But now I've finished updating my computer, so hopefully no one can hack me and move copyrighted Windows binaries onto my system.