public class SingletonClosure extends Closure implements Sequence<Item<?>>
The expression may depend on local variables and on the context item; these values are held in the saved XPathContext object that is kept as part of the Closure, and they will always be read from that object. The expression may also depend on global variables; these are unchanging, so they can be read from the Bindery in the normal way. Expressions that depend on other contextual information, for example the values of position(), last(), current(), current-group(), should not be evaluated using this mechanism: they should always be evaluated eagerly. This means that the Closure does not need to keep a copy of these context variables.
depth, expression, inputIterator, savedXPathContext
Constructor and Description |
---|
SingletonClosure(Expression exp,
XPathContext context)
Constructor should not be called directly, instances should be made using the make() method.
|
Modifier and Type | Method and Description |
---|---|
Item<?> |
asItem()
Return the value in the form of an Item
|
int |
getLength()
Get the length of the sequence
|
Item<?> |
itemAt(int n)
Get the n'th item in the sequence (starting from 0).
|
UnfailingIterator<Item<?>> |
iterate()
Evaluate the expression in a given context to return an iterator over a sequence
|
SingletonClosure |
makeRepeatable()
Ensure that the sequence is in a form where it can be evaluated more than once.
|
ZeroOrOne<Item<?>> |
materialize()
Return a value containing all the items in the sequence returned by this
SequenceIterator
|
getExpression, getSavedXPathContext, head, make, reduce, saveContext, setExpression, setSavedXPathContext
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
asIterable, head
public SingletonClosure(Expression exp, XPathContext context) throws XPathException
exp
- the expression to be lazily evaluatedcontext
- the context in which the expression should be evaluatedXPathException
- if an error occurs saving the dynamic contextpublic UnfailingIterator<Item<?>> iterate() throws XPathException
iterate
in interface Sequence<Item<?>>
iterate
in class Closure
SequenceIterator
, which is
not a Iterator
) over all the itemsXPathException
- in the situation where the sequence is evaluated lazily, and
constructing an iterator over the items causes a dynamic error.public Item<?> asItem() throws XPathException
XPathException
public Item<?> itemAt(int n) throws XPathException
XPathException
public int getLength() throws XPathException
XPathException
public ZeroOrOne<Item<?>> materialize() throws XPathException
materialize
in interface Sequence<Item<?>>
XPathException
- if evaluating the contents of the sequence fails with
a dynamic error.public SingletonClosure makeRepeatable()
Sequence
LazySequence
and Closure
can only be evaluated
once, and this operation causes these to be grounded. However, making it repeatable
is not the same as making it grounded; it does not flush out all errors. Indeed, lazy
evaluation relies on this property, because an expression that has been lifted out of
a loop must not be evaluated unless the loop is executed at least once, to prevent spurious
errors.makeRepeatable
in interface Sequence<Item<?>>
makeRepeatable
in class Closure
Copyright (c) 2004-2020 Saxonica Limited. All rights reserved.