- From: <bugzilla@farnsworth.w3.org>
- Date: Tue, 01 Apr 2008 20:02:33 +0000
- To: public-qt-comments@w3.org
- CC:
------- Comment #10 from jmdyck@ibiblio.org 2008-04-01 20:02 ------- (In reply to comment #9) > > I had presumed from F&O 1.4 that there are four separate fn:abs functions > (or at least four separate signatures that are chosen from at compile time). > Which parts of the specification imply otherwise? XQuery 2.1.1 Static Context Function signatures: Each function is uniquely identified by its expanded QName and its arity (number of parameters). (Echoed in C.1 Static Context Components.) FS 3.1.1 Static Context statEnv.funcType: Because [XPath/XQuery] allows multiple functions with the same name differing in the number of parameters, this environment component maps an expanded QName and an arity to a function signature FunctionSig. So where 4.1.5 / STA / rules 3+4 and 4.1.5 / Dyn Ev / rules 1+2 consult statEnv.funcType for a given FunctionCall (with specific expanded-QName and arity), it yields exactly one function signature (or else fails, if the function name is undefined). There's no way to bring four signatures into the picture. > Should this be marked as a bug against Functions & Operators? I don't think this Bugzilla bug should have its Component changed to F+O, if that's what you're suggesting. But it might be worth a new bug.
Received on Friday, 4 April 2008 10:00:36 UTC