[ 
https://issues.apache.org/jira/browse/XALANC-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461797#comment-13461797
 ] 

Martin Elzen commented on XALANC-733:
-------------------------------------

Looks good to me.  OTOH, there does tend to be one issue when you define a 
static class member like this: it's storage needs to be allocated somewhere, 
usually in the relevant .cpp file.  Eg (assuming its within the XalanLocator 
class), in XalanLocator.cpp there ought to be a line that 'allocates the 
storage', something like: XalanLocator::s_dczero;  

... Was something like that not needed anymore?  OTOH, maybe I'm too used to 
old-fashioned C++ and the above syntax "just works" on recent compilers...
                
> Ensure that XalanLocator::getSystemId() and getPublicId() do not return NULL
> ----------------------------------------------------------------------------
>
>                 Key: XALANC-733
>                 URL: https://issues.apache.org/jira/browse/XALANC-733
>             Project: XalanC
>          Issue Type: Bug
>          Components: XalanC, XPathC
>    Affects Versions: 1.11
>            Reporter: Steven J. Hathaway
>            Assignee: Steven J. Hathaway
>         Attachments: XalanLocator-3.patch, XalanLocator.patch, 
> XalanLocator.patch2
>
>
> The recommended patch to "xalanc/PlatformSupport/XalanLocator.hpp"
> ensures that getSystemId() and getPublicId() do not return NULL pointers.
> XalanC source files that can benefit from the patch include:
> xalanc/PlatformSupport/ProblemListenerBase.cpp
> xalanc/PlatformSupport/XSLException.cpp
> xalanc/XPath/XPathExecutionContextDefault.cpp
> The patch will be submitted shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to