This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: FXPath v0.3 + SAXON Implementation


> From: David.Rosenborg@pantor.com 

> Also, there's a test implementation of FXPath for SAXON:
> 
>   http://www.pantor.com/fxpath/saxon.html
> 
> So now you can try FXPath functions for real.

com:eval is fooling me.

It  transpires that it results in a template match,
moded, with an expression as a param.

so I have

 <xsl:template match="*" mode="com:eval">
    <xsl:param name="expr" select="."/>
    ?????
  </xsl:template>

I'm *guessing* that the function evaluates to the application
of the expression to the node value.
If the 'expression' is something like contains(.,'P')
is it possible to apply that expression within the moded template?
  Or am I wrong again?
(It doesn't smell right, because the return value is cast to a string
  in one of the functions that use it)

Regards DaveP

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]