Subject: Re: [xsl] avoiding assignment statements From: David Carlisle <davidc@xxxxxxxxx> Date: Fri, 8 Dec 2006 14:28:36 GMT |
xslt works rather better if you have structured input rather than a fixed set of flat variables. If you had a parameter show that took a list of elements say <Replicates/><Metadata/> then you could just do <xsl:for-each select="$show"> <xsl:if test="position()!=1">, </xsl:if> <xsl:apply-templates select="."/> </xsl:for-each> where templates macching Replicates woul ddo whatever your pseudo code Output("Reps") does. or in xslt2 you could just have again a single parameter which takes a sequence of strings rather than elements, and again for-each over that. As it is, with scalar params, it's a bit easier to handle in xslt2, as you can easily turn it into the above <xsl:variable name="show" as="element()*"> <xsl:if test="showReplicates=1"><Replicates/></xsl:if> ... </xsl:if> in xslt1 you could do the same with the node-set extension that most systems offer. David
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] avoiding assignment statement, Sam Carleton | Thread | Re: [xsl] avoiding assignment state, Sam Carleton |
[xsl] avoiding assignment statement, Sam Carleton | Date | Re: [xsl] avoiding assignment state, Sam Carleton |
Month |