- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 24 Feb 2010 19:39:49 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9139 --- Comment #3 from Michael Kay <mike@saxonica.com> 2010-02-24 19:39:49 --- I see that rule 3 of dynamic function invocation does in fact invoke rules 3-5 of "function call", which I had previously missed. So as JS says, the remaining question is whether position#0() returns the context position, or throws an error. Note that the question is rather more important in an XSLT context, where there are many more built-in functions that give access to dynamic context information, for example current-group(), regex-group(), and so on. My feeling is that it's better if a dynamic function call always discards the context information, rather than having it depend on which function is being called. -- 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 19:39:51 UTC