Karl Stubsjoen wrote:
What would cause a string() test to fail? I've tested on a simple
xml, like this, with the following test:
Assume we are matching on B
<xsl:if test="string(C/@test)">Yes</xsl:if> You get one Yes.
<A>
<B>
<C/>
<C/>
<C/>
</B>
<B>
<C/>
<C test="yes"/>
<C/>
</B>
</A>
What would you expect to get?
Remember that in the context of xsl:if test, there is a coercion to
Boolean. When there is no @test attribute, the string() will evaluate
to the empty string, which in turn evaluates to false. So I would
expect no Yes for the first <B> and a Yes for the second <B>.
~Chris
--
Chris Maden, text nerd <URL: http://crism.maden.org/ >
“All I ask of living is to have no chains on me,
And all I ask of dying is to go naturally.” — Laura Nyro
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319
--~------------------------------------------------------------------
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>
--~--