rleigh-codelibre commented on pull request #39: URL: https://github.com/apache/xerces-c/pull/39#issuecomment-925360640
I'll get to the review tomorrow. In terms of C++11 support, the stable release does not require it. The master branch (4.0.x) does. You'll see today I merged a PR from last year which requires C++11 `<cstdint>`. While the CMake build tries to enable C++17, C++14 or C++11 (where available), this was the first feature addition which actually used a C++11 feature. While I don't think there is as of yet much discussion about what could be refactored to use C++11 features, previous discussion has focussed upon retaining API compatibility to the maximum extent possible, so I think we will need to be fairly conservative with changes, certainly changes which affect the API or ABI. Since Xerces-C++ did not originally use any of the C++ Standard Library, it does have some fairly archaic design which could certainly be replaced. The memory management in particular. However, it does need to work as a Windows DLL which puts constraints upon use of C++ features which cross DLL boundaries--templates in particular are very tricky if not impossible in many cases to export. But the biggest constraint is developer time and interest. I do have a branch which makes it use `std::thread`. But there are whole categories of wrappers and helpers which could be gutted and replaced with standard equivalents. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
