[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] Nicer way to change context-node than xsl:for-each ?

Subject: Re: [xsl] Nicer way to change context-node than xsl:for-each ?
From: Mukul Gandhi <gandhi.mukul@xxxxxxxxx>
Date: Mon, 7 Dec 2009 07:18:55 +0530

On Sun, Dec 6, 2009 at 5:55 PM, Florent Georges <lists@xxxxxxxxxxxx> wrote:
> B The first difference that come to my mind is that the sequence ctor of a
function is always evaluated in temporary output state.

That's correct I think. The sequence constructor of xsl:function just
computes what to return from the function. The function returns, a
sequence finally (I think, generically any XDM primitive).

Whereas instructions in body of, xsl:call-template actually
contributes to the output of the template (call-template!).


--
Regards,
Mukul Gandhi

Current Thread
Re: [xsl] Nicer way to change context-node than xsl:for-each ?, (continued) Mukul Gandhi - 5 Dec 2009 16:09:57 -0000 Dimitre Novatchev - 5 Dec 2009 17:22:46 -0000 Mukul Gandhi - 6 Dec 2009 02:13:45 -0000 Florent Georges - 6 Dec 2009 12:26:23 -0000 Mukul Gandhi - 7 Dec 2009 01:49:42 -0000 <= Florent Georges - 7 Dec 2009 09:02:18 -0000 Andrew Welch - 7 Dec 2009 10:45:47 -0000 Mukul Gandhi - 7 Dec 2009 13:34:16 -0000 Andrew Welch - 7 Dec 2009 14:32:23 -0000

Current Thread

Re: [xsl] Nicer way to change context-node than xsl:for-each ?, (continued)

<- Previous	Index	Next ->
Re: [xsl] Nicer way to change conte, Florent Georges	Thread	Re: [xsl] Nicer way to change conte, Florent Georges
Re: [xsl] Nicer way to change conte, Florent Georges	Date	Re: [xsl] Nicer way to change conte, Florent Georges
	Month

Re: [xsl] Nicer way to change context-node than xsl:for-each ?

Products

Features

Shop

Resources

Support

Company