Project

Profile

Help

How to connect?
Download (2.28 KB) Statistics
| Branch: | Tag: | Revision:

he / latest10 / hej / net / sf / saxon / expr / instruct / package.html @ 02f8308b

1
<!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
2
<!-- Copyright (c) 2014 Saxonica Limited. -->
3
<!-- This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. -->
4
<!-- If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/. -->
5
<!-- This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0. -->
6
<!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
7

    
8
<html>
9

    
10
<head>
11
    <title>Package overview: net.sf.saxon.expr.instruct</title>
12

    
13
</head>
14

    
15

    
16
<body>
17

    
18
<p>This package provides classes for the compiled representation of the various elements
19
    and other instructions found in an XSLT stylesheet. The same constructs are also used for
20
    evaluating similar constructs in XQuery, in particular, expressions that construct new nodes.</p>
21

    
22
<p>Instances of these classes are constructed when the stylesheet or query is compiled. In the
23
    case of XSLT, the objects
24
    representing the compile-time stylesheet (in package {@link net.sf.saxon.style}) can then be
25
    discarded and garbage-collected.</p>
26

    
27
<p>The most important class is {@link Instruction}, which represents an XSLT Instruction. In most cases
28
    these instructions have a one-to-one relationship with instructions in the original source XSLT
29
    stylesheet, and the names of the subclasses (for example ApplyImports, ApplyTemplates, Choose)
30
    reflect this.</p>
31

    
32
<p>In XSLT 1.0, XSLT instructions and XPath expressions were quite distinct, and were evaluated in different
33
    ways: XSLT instructions in "push" mode (they were described as "writing to the result tree"), and XPath expressions
34
    in "pull" mode (reading from the source tree). This distinction is no longer present in the XSLT 2.0 processing
35
    model, and the boundary between the <code>Instruction</code> and <code>Expression</code> classes is therefore
36
    a rather fuzzy one. Both instructions and expressions can now be evaluated in either push or pull mode.
37
    Flow-of-control constructs such as conditional expressions and FOR expressions are evaluated in either mode
38
    depending on their parent expression.</p>
39

    
40
</body>
41
</html>
(74-74/74)