There is no memory leak.
The m_stylesheetParams are intended to be sticky.
The user application should perform the m_stylesheetParams.clear()
before assigning new top-level parameters.
The reset() function is intended for reuse of an existing
XSLTEngineImpl instance for a new transformation and
preserves m_stylesheetParams so the structure does not
have to be reloaded between transformations using the
same class XSLTEngineImpl instance.
- Steve
On 10/10/2011 11:58 AM, shath...@e-z.net wrote:
Is there a memory problem here? -- analysis needed!
XSLT/XSLTEngineImpl.c
Constructor XSLTEngineImpl::XSLTEngineImpl(...) initializes
m_topLevelParams(theManager)
m_stylesheetParams(theManager)
But the reset XSLTEngineImpl::reset() only clears
m_topLevelParams.clear();
Should we also add the following to the reset()?
m_stylesheetParams.clear();
-----------
Steven J.Hathaway
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
