You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Roger Leigh (JIRA)" <ji...@apache.org> on 2019/05/26 19:49:00 UTC
[jira] [Commented] (XALANC-775) Xalan is incompatible with C++17
[ https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848513#comment-16848513 ]
Roger Leigh commented on XALANC-775:
------------------------------------
Note that this was applied to the git master branch today. If you would like to try it out, I'd appreciate some testing of the changes.
> Xalan is incompatible with C++17
> --------------------------------
>
> Key: XALANC-775
> URL: https://issues.apache.org/jira/browse/XALANC-775
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
> Affects Versions: 1.11
> Reporter: Hermann Walth
> Assignee: Steven J. Hathaway
> Priority: Major
> Attachments: 0001-Remove-usage-of-std-unary_function-and-std-binary_fu.patch, 0002-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch
>
>
> In C++ 17, the template classes std::unary_function and std::binary_function have been removed. Since Xalan derives multiple classes from these classes, using it with the flag -std=c++17 fails.
> This does not just affect compilation of Xalan itself, but any project that includes Xalan's header files, as including those files causes errors about the nonexisting symbol std::unary_function.
> I'm currently working on a project that uses Xalan, and this issue is stopping us from moving our codebase to C++17.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org