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 2018/02/26 22:03:00 UTC
[jira] [Commented] (XALANC-779) Use xercesc namespace
unconditionally
[ https://issues.apache.org/jira/browse/XALANC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377669#comment-16377669 ]
Roger Leigh commented on XALANC-779:
------------------------------------
Note this is a companion to the changes in https://issues.apache.org/jira/browse/XERCESC-2138 which drops the use of these macros in Xerces-C++ by dropping compatibility workarounds for pre-C++98 compilers two decades back.
> Use xercesc namespace unconditionally
> -------------------------------------
>
> Key: XALANC-779
> URL: https://issues.apache.org/jira/browse/XALANC-779
> Project: XalanC
> Issue Type: Improvement
> Components: XalanC
> Reporter: Roger Leigh
> Assignee: Steven J. Hathaway
> Priority: Major
> Attachments: 0001-Use-xercesc-namespace-unconditionally.patch, 0002-Remove-XALAN_USING_XERCES-macro.patch, 0003-Remove-XALAN_DECLARE_XERCES_CLASS-macro.patch, 0004-Remove-XALAN_DECLARE_XERCES_STRUCT-macro.patch, 0005-Remove-XERCES_HAS_CPP_NAMESPACE-check.patch, 0006-Drop-use-of-XERCES_CPP_NAMESPACE_USE.patch
>
>
> There are no current compilers which lack namespace support, and all current xerces-c builds are using namespaces by default, making this macro redundant and overly complex.
>
> This should not have any portability or compatibility concerns given the ubiquity of namespace support on contemporary systems.
--
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