Re: Implementing XPointer Resolution With saxon:evalua

Jeni Tennison wrote:

> 
> One of the rules about EXSLT function definitions is that the
> processor must only encounter one func:result instruction when
> evaluating the function body. This is to preserve the usual
> side-effect-free nature of XSLT (and is why func:result is called
> func:result rather than func:return).

I thought I saw an example in the EXSLT stuff of using func:result in
this way, but you're right, the docs certainly don't support that use
(although it seemed intuitively correct to me by analogy to the way that
RTFs are constructed w/in templates--that is, all the occurrences of
func:result from a *single place* in the initial template are
automatically concatenated to create a single result node set).

Clearly I need to add more test cases....

Thanks,

E.
-- 
W. Eliot Kimber, eliot@xxxxxxxxxx
Consultant, ISOGEN International

1016 La Posada Dr., Suite 240
Austin, TX  78752 Phone: 512.656.4139

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