- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 24 Feb 2010 17:38:59 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9139
Summary: [XPath 2.1] Dynamic function calls and context
Product: XPath / XQuery / XSLT
Version: Working drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XPath 2.1
AssignedTo: jonathan.robie@redhat.com
ReportedBy: mike@saxonica.com
QAContact: public-qt-comments@w3.org
The rules for dynamic function calls should make it clear that no context
information is passed from the caller's context to the callee's context other
than that explicitly mentioned (the variables in the closure). This has the
consequence that a dynamic call to a contextual core function like position()
is not useful (in fact, it will always fail).
The only place where we say that the focus is cleared on a function call is in
3.1.5 Function Calls, rule 4:
"During evaluation of a function body, the focus (context item, context
position, and context size) is undefined, except where it is defined by some
expression inside the function body."
but this rule (appearing where it does) only applies to explicit calls on
"user-declared functions": it does not apply to dynamic calls on user-declared
functions, or to dynamic calls on inline functions, or to dynamic calls on
built-in functions such as position(). It should apply to all these cases.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 24 February 2010 17:39:00 UTC