Subject: Re: [xsl] current-dateTime() From: Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx> Date: Fri, 18 Apr 2008 14:35:53 +0100 |
>>>>> "Dimitre" == Dimitre Novatchev <dnovatchev@xxxxxxxxx> writes: Dimitre> $vX and $vY, Dimitre> such that $vY is defined as: <xsl:variable name="$vY" Dimitre> select="f:someFun($vX)" as="someType"/> Dimitre> Then it is true that: Dimitre> creationTime($vY) > creationTime($vX) No - not creation time. End-of-evaluation time, yes. Dimitre> Using this simple principle of dependency (causual) Dimitre> ordering, one can write code that is guaranteed to be Dimitre> evaluated in a certain sequential manner. With the correction above. Dimitre> XSLT supports a more specific run-time Dimitre> serialization. Let's have the following tree: Dimitre> <a> <b> <c> <d/> </c> </b> </a> Dimitre> and templates tmpl-matchA, tmpl-matchB, tmpl-matchC, Dimitre> tmpl-matchD that match correspondingly the nodes a,b,c Dimitre> and d. Dimitre> Then it is true that: Dimitre> strtRunTime(tmpl-matchA) < strtRunTime(tmpl-matchB) < Dimitre> strtRunTime(tmpl-matchC) < strtRunTime(tmpl-matchD) No, this is not guaranteed in all cases. However there are some usage patterns which will guarantee this. -- Colin Adams Preston Lancashire
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] current-dateTime(), David Carlisle | Thread | Re: [xsl] current-dateTime(), Liam Quin |
Re: [xsl] current-dateTime(), David Carlisle | Date | Re: [xsl] current-dateTime(), Michael Ludwig |
Month |