You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by sc...@us.ibm.com on 2002/04/05 21:41:03 UTC
Re: Xalan CVS / Extension Functions / XSLTC
Peter Royal <pr...@managingpartners.com> wrote:
> BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
> stylesheet i was trying to optimize),
I suspect that's mainly the redundant expression elimination I checked in.
> *BUT* the extension function we use in
> xsp.xsl wasn't working correctly, I was just getting empty strings.
Is this a Xalan bug? Has it been reported in bugzilla? If it has been,
give me the bug number and I'll look into it.
-scott
Re: Xalan CVS / Extension Functions / XSLTC
Posted by Peter Royal <pr...@managingpartners.com>.
On Friday 05 April 2002 02:41 pm, scott_boag@us.ibm.com wrote:
> Peter Royal <pr...@managingpartners.com> wrote:
> > BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
> > stylesheet i was trying to optimize),
>
> I suspect that's mainly the redundant expression elimination I checked in.
Good work! (it was string-matching in an xsl:if test that was my specific
speedup)
> > *BUT* the extension function we use in
> > xsp.xsl wasn't working correctly, I was just getting empty strings.
>
> Is this a Xalan bug? Has it been reported in bugzilla? If it has been,
> give me the bug number and I'll look into it.
I believe so now, I just wanted to verify with cocoon-dev before opening a
Xalan bug. Its now bug #7776.
-peter
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Xalan CVS / Extension Functions / XSLTC
Posted by Peter Royal <pr...@managingpartners.com>.
On Friday 05 April 2002 02:41 pm, scott_boag@us.ibm.com wrote:
> Peter Royal <pr...@managingpartners.com> wrote:
> > BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
> > stylesheet i was trying to optimize),
>
> I suspect that's mainly the redundant expression elimination I checked in.
Good work! (it was string-matching in an xsl:if test that was my specific
speedup)
> > *BUT* the extension function we use in
> > xsp.xsl wasn't working correctly, I was just getting empty strings.
>
> Is this a Xalan bug? Has it been reported in bugzilla? If it has been,
> give me the bug number and I'll look into it.
I believe so now, I just wanted to verify with cocoon-dev before opening a
Xalan bug. Its now bug #7776.
-peter
--
peter royal -> proyal@managingpartners.com