Re: [xslt] crash in libxslt 1.0.9

On Thu, Mar 07, 2002 at 11:48:51AM -0700, Vakoc, Mark wrote:
> I was entering a bug as I received this email
>  :)
> >   I think the problem is called "dynamic code generation".
> > Basically exslt:function now allows to dynamically extend the XSLT
> > code at run-time. Everything looked fine because the new document 
> > were also kept in the document list which is kept im memory till the
> > end of the processing.
> Not sure why you mention exsl:function as that isn't used anywhere, just
> exsl:node-set

  Seems to indicate I too tired to do any more work today...

> I have been digging in trying to figure this out, and simplified the source
> stylesheet a little bit.  Attached are two stylesheets (replacements for
> style.xsl), broken.xsl and works.xsl.  They are nearly identical, except
> where
> -- in broken.xsl --
> <xsl:variable name="var">
>   stuff (see attachment for complete)
> </xsl:variable>
> <xsl:apply-templates select="exsl:node-set($var)"/>
> -- in works.xsl
> <xsl:variable name="var">
>   stuff (see attachment for complete)
> </xsl:variable>
> <xsl:variable name="var2" select="exsl:node-set($var)"/>
> <xsl:apply-templates select="$var2"/>
> I will continue to dig around to hopefully find an answer as I use this
> 'dynamic' approach in many stylesheets.  Do you have any pointers where to
> begin looking (this is, why the two examples behave differently?)

  Well I will need to use a debugger.
You can run xsltproc -v to see what is the order of operation taken till the


Daniel Veillard      | Red Hat Network  | libxml Gnome XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]