This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
AW: regarding variables and axis
- From: "Fries, Markus, fiscus GmbH, Bonn" <M dot Fries at fiscus dot info>
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 22 Mar 2002 16:40:53 +0100
- Subject: AW: [xsl] regarding variables and axis
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi!
no idea about overhead by variables...
I can help you with a simpler XPATH for the other one:
../../childelement1/text()
Markus
-----Ursprüngliche Nachricht-----
Von: william locksman [mailto:vsd18@rediffmail.com]
Gesendet: Freitag, 22. März 2002 16:24
An: xsl-list@lists.mulberrytech.com
Betreff: [xsl] regarding variables and axis
Dear members
The following are my questions.
1.Will unnecesary variable declaration contribute to any overhead
in terms of processing performance etc??
2.if i have an xml structure like this:
<root>
<parentelement>
<childelement1>text in child1</childelement1>
<childelement>
<name></name>
</childelement>
</parentelement>
</root>
If context node is <name>(i got there through a for loop),then how
do i print the text in <childelement1>
i understand ancestor would not get me to childelement1..
how do i then reach to main element..
alternatively i thought of a solution of getting there through
ancestor::parentelement/childelement1/text()
It works but i am not sure if it is the right way to do it.
any suggestions regarding this ??
many thanks in advance
Bill
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list