On 26/04/2017 01:30, Cantor, Scott wrote:
On 4/25/17, 3:17 PM, "Roger Leigh" wrote:
That said, I'd not be averse to including support for standard C++;
using Xerces is often a bugbear due to its age. All our code is now
C++11, with RAII wrappers to make Xerces play nicely. Primarily the
lac
On 4/26/17, 4:04 AM, "Roger Leigh" wrote:
> Agreed that just moving up to C++98 standard types in and of itself
> would be greatly beneficial. There should be no portability barrier to
> achieving that.
No, definitely not. I've been using the STL and Boost for years now on many
platforms.
>
I would have been writing the original version of the parser in about 98
probably, so C++98 would have only just come into being. Though, the thing with
not just sharing allocated memory with the containing application was added
later. I didn't write it that way at the start and wouldn't have ev
[
https://issues.apache.org/jira/browse/XERCESC-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985938#comment-15985938
]
Alex Phillips commented on XERCESC-2091:
I confirmed the Exception occurs on 64-
