|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: going crazy
> Weird Behavior: Possibly non-intuitive, but probably correct. > > count( (//BADUSERS/BADUSER)[2] ) returns 1 This finds all the //BADUSERS/BADUSER elements, then finds the second of them, then counts how many are left. The result will be 1 if there are two or more //BADUSERS/BADUSER elements, else 0. > > count( (//BADUSERS/BADUSER)[2]/* ) returns nothing I'm not sure what you mean by "nothing", it should always return a number, specifically the number of child elements that the second //BADUSERS/BADUSER has. > > count( //BADUSERS/BADUSER[2] ) returns 0 This counts the number of BADUSER elements that are the second BADUSER child of a BADUSERS element. > > count( //BADUSERS/BADUSER[1] ) returns 3 This counts the number of BADUSER elements that are the first BADUSER child of a BADUSERS element. Mike Kay PS: Round here, we are discouraged from making moral judgements on our users. Shame really. > > There are 3 BADUSER elements. Can anyone shed some light on > this? I am using XSL:P. > > Thanks, > Natalie > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








