W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2010

[Bug 9139] [XPath 2.1] Dynamic function calls and context

From: <bugzilla@wiggum.w3.org>
Date: Wed, 03 Mar 2010 21:54:28 +0000
To: public-qt-comments@w3.org
Message-Id: <E1NmwWS-00061J-Ui@wiggum.w3.org>

--- Comment #12 from John Snelson <john.snelson@oracle.com>  2010-03-03 21:54:28 ---
(In reply to comment #11)
> If the example were
> a.xq:   declare function f() as xs:string { fn:static-base-uri() }
> b.xq:   f()
> we'd expect "a.xq", wouldn't we? I'm not sure why the first example is
> different. In both cases, the built-in function is referenced from module a, so
> that determines the static context that it's evaluated against when it's
> invoked.

For functions that return things from the static context, I've got to say that
I agree with Michael Dyck. It would be extremely unfortunate if I couldn't tell
at compile time everywhere that needed a given piece of information from the
static context. One could argue that it would be a contradiction in terms.

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, 3 March 2010 21:54:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:30 UTC