Got the bug report -- thanks. In this case, it's easy to figure out when
the variable goes out of scope. Other situations are not so
straightforward.
I'm looking at several ways to fix this. Unfortunately, all will involve a
slight performance hit in the common cases where there aren't so many RTFs.
It's a matter to choosing the right way to go.
Yes, I'm the only one left working on the C++ processor. Anyone interested
in working on Xalan-C++ should volunteer some time -- there are lots of
things to work on.
Dave
|---------+--------------------------->
| | Holger Floerke |
| | <floerke@doctron|
| | ic.de> |
| | |
| | 03/27/2002 11:59|
| | PM |
| | Please respond |
| | to xalan-dev |
| | |
|---------+--------------------------->
>---------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: Re: Transforming memory grows (Xalan-C)
|
>---------------------------------------------------------------------------------------------------------------------------|
>At any rate, it's _always_ more efficient to avoid the creation of result
>tree fragments, so you should always use this:
>
> <xsl:with-param name="arg1" select="substring(.,2)"/>
>
>instead of this:
>
><xsl:with-param name="arg1">
> <xsl:value-of select="substring(.,2)"/>
></xsl:with-param>
>
>whenever you can. This is not a "special" use of xsl:with-param.
Ok, "special" was the wrong term. I meant "another".
>By the way, don't underestimate the difficulty of tracking variables in a
>complex language like XSLT -- it's not as easy as it might seem.
Ups, I thought it would be very easy in XSLT, because no one can change the
variable and if I leave the context, the variable will be destroied.
>If you can post your document and stylesheet attached to a Bugzilla
report,
>I will use it when I start the RTF optimization work.
Bug #7556. I have posted an example of using a variable with memory grow,
too.
> Dave
Are you the only one managing Xalan-C? I would like to thank you for your
work so far. Do you see any possibility to involve some other people
improving Xalan-C? Xalan-C is a powerful and good thing. Many people using
Xalan-C. I wouldn't like to see the stagnation of Xalan-C.
HolgeR
