This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: looping


David Carlisle wrote:
>you are relying on the implicit coercion from string to number here,
>simpler to give the number directly
>
>  <xsl:param name="start-val" select="0"/>

As far as I can tell, there are no type restrictions associated with the
value returned by the expression within the select attribute of xsl:param.

Wouldn't <xsl:param name="start-val" select="0"/> cause the parser to search
for a child named "0" within the context node?  Can it be safely assumed
that if such a node does not exist the parser will return a numeric value of
zero?

If you're concerned about relying upon implicit type conversion, couldn't
you use the following instead?

  <xsl:param name="start-val" select="number(0)"/>
  
Bill Wade


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]