Previous (XmlNode function): Difference between revisions
m (1 revision) |
m (edits, tags and links) |
||
Line 1: | Line 1: | ||
{{Template:XmlNode:Previous subtitle}} | {{Template:XmlNode:Previous subtitle}} | ||
<var>Previous</var> returns the previous <var>XmlNode</var> with the same parent as the method object. | |||
<ul> | <ul> | ||
<li>If the method object is a non-Attribute node, the previous <var>XmlNode</var> is | <li>If the method object is a non-<var>Attribute</var> node, the previous <var>XmlNode</var> is the previous sibling (in document order) of the method object. This is exactly the same as the node returned by <var>[[SelectSingleNode_(XmlDoc/XmlNode_function)|selectSingleNode]]</var> with <code>'preceding-sibling::node()[1]'</code> as its [[XPath]] argument. This is demonstrated below in item [[#PreviousEx1|"example 1"]] . | ||
the previous sibling (in document order) of the method object. | <li>If the method object is an <var>Attribute</var> node, the previous <var>XmlNode</var> is the preceding <var>Attribute</var> node produced if the <var>Element</var> containing the method object were serialized in "normal" (that is, ''not'' ExclCanonical) order. | ||
This is exactly the same as the node returned by | |||
with < | |||
This is demonstrated below in item [[ | |||
<li>If the method object is an Attribute node, the previous <var>XmlNode</var> is the | |||
preceding Attribute | |||
node produced if the Element containing the method object | |||
were serialized in "normal" (that is, ''not'' ExclCanonical) order. | |||
<li>If no "previous" node exists, the <var>Previous</var> method returns a Null. | <li>If no "previous" node exists, the <var>Previous</var> method returns a Null. | ||
</ul> | </ul> | ||
==Syntax== | ==Syntax== | ||
{{Template:XmlNode:Previous syntax}} | {{Template:XmlNode:Previous syntax}} | ||
Line 22: | Line 12: | ||
<table class="syntaxTable"> | <table class="syntaxTable"> | ||
<tr><th>%outNod</th> | <tr><th>%outNod</th> | ||
<td>An <var>XmlNode</var>, which will be set to point to the returned node. </td></tr> | <td>An <var>XmlNode</var>, which will be set to point to the returned node.</td></tr> | ||
<tr><th>nod</th> | <tr><th>nod</th> | ||
<td>An <var>XmlNode</var> expression.</td></tr> | <td>An <var>XmlNode</var> expression.</td></tr> | ||
Line 29: | Line 19: | ||
==Usage notes== | ==Usage notes== | ||
<ul> | <ul> | ||
<li>The XPath recommendation specifies that | <li>The XPath recommendation specifies that the following-sibling and preceding-sibling axes are the empty nodeSet if the context node is an <var>Attribute</var> node. The <var>[[Next_(XmlNode_function)|Next]]</var> and <var>Previous</var> methods are available if you want to traverse the <var>Attribute</var> nodes of an <var>Element</var>, as a better approach than using the following-sibling and preceding-sibling axes in an XPath argument to a <var>[[SelectNodes_(XmlDoc/XmlNode_function)|selectNodes]]</var> or <var>SelectSingleNode</var> method. See: [[#PreviousEx2|"example 2"]]. | ||
the following-sibling and preceding-sibling axes are the empty nodeSet if | <li><var>Previous</var> is new as of <var class="product">[[Sirius Mods]]</var> Version 7.0. | ||
the context node is an Attribute node. | |||
The | |||
are available if you want to traverse the Attribute nodes of an Element, as | |||
a better approach than using the following | |||
axes in an XPath argument to a | |||
See example [[ | |||
</ul> | </ul> | ||
==Examples== | ==Examples== | ||
<ol> | <ol><li><div id="PreviousEx1"></div>Given the following document: | ||
<li>Given the following document: | |||
<p class="code"><top> | <p class="code"><top> | ||
<a/> | <a/> | ||
Line 50: | Line 33: | ||
</top> | </top> | ||
</p> | </p> | ||
To select the node that precedes <var>Element</var> <code>c</code>, you can use a sequence of statements like the following: | |||
To select the node that precedes Element < | <p class="code">%n1 is object XmlNode | ||
a sequence of statements like the following: | %n1 = %doc:selectSingleNode('/*/*[3]') | ||
<p class="code">%n1 is object | print 'Here is node 3:' | ||
%n1 = %doc: | %n1:[[Print_(XmlDoc/XmlNode_subroutine)|print]] | ||
%n2 = %n1:previous | |||
%n1: | print 'Here is the node previous to 3:' | ||
%n2 = %n1: | %n2:print | ||
%n2: | |||
</p> | </p> | ||
The result is: | The result is: | ||
<p class="output">Here is node 3: | <p class="output">Here is node 3: | ||
Line 68: | Line 48: | ||
<b/> | <b/> | ||
</p> | </p> | ||
'''Note:''' You might expect a statement sequence like this next one to also obtain the <code>b</code> node as above: | |||
'''Note:''' | <p class="code">%n2 = %n1:selectSingleNode('preceding-sibling::node()') | ||
You might expect a statement sequence like | print 'Here is the preceding-sib to 3:' | ||
this next one to also obtain the < | %n2:print | ||
<p class="code">%n2 = %n1: | |||
%n2: | |||
</p> | </p> | ||
However, this is the result: | However, this is the result: | ||
<p class="code">Here is the preceding-sib to 3: | <p class="code">Here is the preceding-sib to 3: | ||
<a/> | <a/> | ||
</p> | </p> | ||
The preceding-sibling axis generates resultant nodes in reverse document order (in this case, <code>b</code>, then <code>a</code>), which is probably what you intuitively expect. However, the <var>SelectSingleNode</var> statement selects the first of these two generated nodes <i>in document order</i>. To use <var>SelectSingleNode</var> to select the adjacent preceding sibling node, | |||
The preceding-sibling axis generates resultant nodes in reverse document | |||
order (in this case, < | |||
you intuitively expect. | |||
However, the SelectSingleNode statement selects the first of these two | |||
generated nodes | |||
To use SelectSingleNode to select the adjacent preceding sibling node, | |||
use a predicate so the XPath argument selects the (only) node you want: | use a predicate so the XPath argument selects the (only) node you want: | ||
<p class="code">%n2 = %n1: | <p class="code">%n2 = %n1:selectSingleNode('preceding-sibling::node()[1]') | ||
</p> | </p> | ||
<li>Given the following document: | <li><div id="PreviousEx2"></div>Given the following document: | ||
<p class="code"><top> | <p class="code"><top> | ||
<F b1="b1" b2="b2" b3="b3" b4="b4"/> | <F b1="b1" b2="b2" b3="b3" b4="b4"/> | ||
</top> | </top> | ||
</p> | </p> | ||
To select the <var>Attribute</var> node that precedes <var>Attribute</var> <code>b3</code>, you can use a sequence of statements like the following: | |||
To select the Attribute node that precedes Attribute < | <p class="code">%n1 = %doc:selectSingleNode('/*/F/@b3'):<var>Previous</var> | ||
a sequence of statements like the following: | print 'Here is attribute previous to b3:' | ||
<p class="code">%n1 = %doc: | %n1:print | ||
%n1: | |||
</p> | </p> | ||
The result is: | The result is: | ||
<p class="output">Here is attribute previous to b3: | <p class="output">Here is attribute previous to b3: | ||
b2="b2" | b2="b2" | ||
</p> | </p> | ||
'''Note:''' | '''Note:''' | ||
The preceding-sibling axis does ''not'' locate | The preceding-sibling axis does ''not'' locate ''Attribute'' nodes. The following statement causes a request cancellation: | ||
''Attribute'' nodes. | <p class="code">%n2 = %n1:selectSingleNode('preceding-sibling::node()[1]') | ||
The following statement causes a request cancellation: | |||
<p class="code">%n2 = %n1: | |||
</p> | </p> | ||
</ol> | </ol> | ||
==See also== | ==See also== | ||
{{Template:XmlNode:Previous footer}} | {{Template:XmlNode:Previous footer}} |
Revision as of 03:26, 29 May 2011
Get node previous to this node (XmlNode class)
Previous returns the previous XmlNode with the same parent as the method object.
- If the method object is a non-Attribute node, the previous XmlNode is the previous sibling (in document order) of the method object. This is exactly the same as the node returned by selectSingleNode with
'preceding-sibling::node()[1]'
as its XPath argument. This is demonstrated below in item "example 1" . - If the method object is an Attribute node, the previous XmlNode is the preceding Attribute node produced if the Element containing the method object were serialized in "normal" (that is, not ExclCanonical) order.
- If no "previous" node exists, the Previous method returns a Null.
Syntax
%outNod = nod:Previous
Syntax terms
%outNod | An XmlNode, which will be set to point to the returned node. |
---|---|
nod | An XmlNode expression. |
Usage notes
- The XPath recommendation specifies that the following-sibling and preceding-sibling axes are the empty nodeSet if the context node is an Attribute node. The Next and Previous methods are available if you want to traverse the Attribute nodes of an Element, as a better approach than using the following-sibling and preceding-sibling axes in an XPath argument to a selectNodes or SelectSingleNode method. See: "example 2".
- Previous is new as of Sirius Mods Version 7.0.
Examples
- Given the following document:
<top> <a/> <c/> <d/> <e/> </top>
To select the node that precedes Element
c
, you can use a sequence of statements like the following:%n1 is object XmlNode %n1 = %doc:selectSingleNode('/*/*[3]') print 'Here is node 3:' %n1:print %n2 = %n1:previous print 'Here is the node previous to 3:' %n2:print
The result is:
Here is node 3: <c/> Here is the node previous to 3:
Note: You might expect a statement sequence like this next one to also obtain the
b
node as above:%n2 = %n1:selectSingleNode('preceding-sibling::node()') print 'Here is the preceding-sib to 3:' %n2:print
However, this is the result:
Here is the preceding-sib to 3: <a/>
The preceding-sibling axis generates resultant nodes in reverse document order (in this case,
b
, thena
), which is probably what you intuitively expect. However, the SelectSingleNode statement selects the first of these two generated nodes in document order. To use SelectSingleNode to select the adjacent preceding sibling node, use a predicate so the XPath argument selects the (only) node you want:%n2 = %n1:selectSingleNode('preceding-sibling::node()[1]')
- Given the following document:
<top> <F b1="b1" b2="b2" b3="b3" b4="b4"/> </top>
To select the Attribute node that precedes Attribute
b3
, you can use a sequence of statements like the following:%n1 = %doc:selectSingleNode('/*/F/@b3'):Previous print 'Here is attribute previous to b3:' %n1:print
The result is:
Here is attribute previous to b3: b2="b2"
Note: The preceding-sibling axis does not locate Attribute nodes. The following statement causes a request cancellation:
%n2 = %n1:selectSingleNode('preceding-sibling::node()[1]')