Xstring is created with already cached number
---------------------------------------------
Key: XALANC-691
URL: https://issues.apache.org/jira/browse/XALANC-691
Project: XalanC
Issue Type: Bug
Affects Versions: 1.10
Reporter: Moddy Te'eni
Priority: Minor
XObjectFactoryDefault::createString(const XalanDOMString&) may return an
Xstring object from the cache, while keeping m_cachedNumberValue from
previously used string. Therefore, num() returns a wrong result.
possible workaround is using XObjectFactoryDefault::createString( const
XalanDOMChar*, unsigned int)
I encountered it when writing an external function, and using it later with
"myFunction() > 5".
see also
http://www.nabble.com/problem-in-cached-numbers-in-Xstring---td24034446.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
