- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 24 Feb 2010 18:13:17 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9139 Jonathan Robie <jonathan.robie@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.robie@redhat.com --- Comment #2 from Jonathan Robie <jonathan.robie@redhat.com> 2010-02-24 18:13:17 --- (In reply to comment #0) > 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. I disagree - the rules for evaluation of a dynamic function are these: A dynamic function invocation is evaluated as follows: 1. Argument values are calculated for the function item using rules 1 and 2 for evaluation of a function call as defined in 3.1.5 Function Calls. 2. The set of variable values from the function item's closure are added to the dynamic context with a scope of the invocation of the function. 3. The function from the function item is evaluated using the argument values according to rules 3 - 5 for evaluation of a function call as defined in 3.1.5 Function Calls. When we evaluate rules 3 - 5 above, that includes rule 4, which you reference above. -- 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 18:13:19 UTC