- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 16:46:50 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10876
Summary: [XQuery11] Is it valid to have conflicting private
functions in two different modules?
Product: XPath / XQuery / XSLT
Version: Member-only Editors Drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 1.1
AssignedTo: jonathan.robie@redhat.com
ReportedBy: oliver@cbcl.co.uk
QAContact: public-qt-comments@w3.org
Group: XSLXQuery_WG
Section 4.12 states:
It is a static error if the expanded QName and arity of a function declared in
an imported module are respectively equal to the expanded QName and arity of a
function declared in the importing module or in another imported module (even
if the declarations are consistent) [err:XQST0034].
Should this be an error if two modules both have a private function with the
same name. My personal inclination is that it shouldn't since they are only in
scope within their respective modules.
To enforce this the text should be changed to:
It is a static error if the expanded QName and arity of a public function
declared in an imported module are respectively equal to the expanded QName and
arity of a function declared in the importing module or the expanded QName and
arity of a public function declared in in another imported module (even if the
declarations are consistent) [err:XQST0034].
Otherwise we should have a note explaining that this also applies to private
functions.
Depending on the outcome of bug #10875 the same change will need to be made for
global variables.
--
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 Thursday, 30 September 2010 16:46:53 UTC