[ 
https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hermann Walth updated XALANC-775:
---------------------------------
    Description: 
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.

  was:
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.


> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to