in the code fragment I posted, I would propose the following change,
you may use:
<xsl:value-of select="false()" /> &
<xsl:value-of select="true()" />
instead of
<xsl:value-of select="'false'" />
<xsl:value-of select="'true'" />
This didn't struck me earlier :)
Regarding XSLT 2.0 vs 1.0, IMHO I would say the 2.0 version is much
better by design and increases programmer productivity considerably.
Here's a little anecdotal evidence:
I like this style of writing in 2.0
<xsl:variable name="x" select="fn:findSomething()" />
over
<xsl:variable name="x">
<xsl:call-template name="findSomething" />
</xsl:variable>
in 1.0
On Fri, Aug 27, 2010 at 8:31 AM,
<pankaj(_dot_)c(_at_)thomsondigital(_dot_)com> wrote:
Yet another fine sample.
If you can, I encourage to move to a 2.0 environment (unless you are
programming for a browser) :)
I personally always use and prefer 2.0 but for this particular case I've
been asked to use 1.0. Some people still prefer old technologies over
latest ones :-)
Thanks anyway.
Pankaj
--
Regards,
Mukul Gandhi
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--