Re: Designs for XSLT functions (Was: Re: RE: syntax su

I ran it with Saxon 5.5.1

but to be honest I am not sure.

I am never sure when result tree fragments are returned and when
nodesets.
At this moment I am using an empirical test: if Saxon returns nodeset
then it 
is O.K. :)
I am so glad these ugly fragment ghosts disappear from 1.1



Francis Norton wrote:
> 
> Miloslav Nic wrote:
> >
> > > I agree that for string manipulation, there's not much call for
> > > anything very sophisticated, and you can always call out to a named
> > > template if you need to.  However, for node-set manipulation that's
> > > not always an option - you can't get a named template to return a node
> > > set.
> >
> > Actually you can:
> >
> 
> ---
> C:\xml>saxon nodeset.xslt nodeset.xslt
> <?xml version="1.0" encoding="UTF-8"?>2
> 
> C:\xml>msxsl nodeset.xslt nodeset.xslt
> <?xml version="1.0" encoding="UTF-8"?>
> 
> Error occurred while executing stylesheet 'nodeset.xslt'.
> 
> Code:   0x80004005
> Reference to variable or parameter 'xxx' must evaluate to a node list.
> 
> C:\xml>
> ---
> 
> Well, you can in Saxon 6.2 (which includes 1.1 support, though this
> shouldn't apply given the version="1.0") but not in MSXML3 - are you
> sure this is kosher?
> 
> Francis.
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

-- 
******************************************
<firstName> Miloslav </firstName>    
<surname>   Nic      </surname>     

<mail>    nicmila@xxxxxxxxx    </mail>   
<support> http://www.zvon.org  </support>
<zvonMailingList> 
    http://www.zvon.org/index.php?nav_id=4 
</zvonMailingList>

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