I think there is a problem in XObjectFactoryDefault::createString(const
XalanDOMString& theValue).
I call it from an extension-function that I wrote. After a few times I call
it, it retuens a string object that came from the cache that already has
m_cachedNumberValue of a previous call. So if my expression is e.g.
"myFunction() > 5", i get wrong results.
I overcame my problem by calling XObjectFactoryDefault::createString(
const XalanDOMChar* theValue,
unsigned int theLength)
that doesnt use m_xstringCache.
Am I doing something wrong or is it a bug?
I'm using Xalan-c 1.10
Thanks, Moddy.
--
View this message in context:
http://www.nabble.com/problem-in-cached-numbers-in-Xstring---tp24034446p24034446.html
Sent from the Xalan - C - Users mailing list archive at Nabble.com.
