[Bug 7864] New: [XQuery 1.1] Unclear whether both user-defined and external functions can be both public and private

View: New views
3 Messages — Rating Filter:   Alert me  

[Bug 7864] New: [XQuery 1.1] Unclear whether both user-defined and external functions can be both public and private

by Bugzilla from bugzilla@wiggum.w3.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7864

           Summary: [XQuery 1.1] Unclear whether both user-defined and
                    external functions can be both public and private
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 1.1
        AssignedTo: jonathan.robie@...
        ReportedBy: jim.melton@...
         QAContact: public-qt-comments@...


In the WD of XQuery 1.1 currently being prepared for internal WG review, the
5th paragraph of Section 4.17, Function Declaration, says:

A function declaration may specify that a function is private or public (which
is the default). [Definition: A private function is hidden from module import,
which can not import it into the function signatures of another module. ]
[Definition: A public function is accessible to module import, which can import
it into the function signatures of another module. ]

EBNF production [31] allows, and the quoted paragraph suggests, that both
user-defined functions and external functions are allowed to be either private
functions or public functions.  However, an admittedly brief scan of the
minutes recording the acceptance of private functions did not reveal whether
the WG intended for this to be the case, or if only declarations of
user-defined functions were to have the option specified.


--
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.


[Bug 7864] [XQuery 1.1] Unclear whether both user-defined and external functions can be both public and private

by Bugzilla from bugzilla@wiggum.w3.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7864


John Snelson <john.snelson@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john.snelson@...




--- Comment #1 from John Snelson <john.snelson@...>  2009-10-12 20:17:50 ---
I don't think the WG discussed that. My opinion is that there's no reason not
to allow private external functions - for instance some internal parts of a
module that interfaces with the hardware may be written as external functions.


--
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.


[Bug 7864] [XQuery 1.1] Unclear whether both user-defined and external functions can be both public and private

by Bugzilla from bugzilla@wiggum.w3.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7864


Jonathan Robie <jonathan.robie@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Jonathan Robie <jonathan.robie@...>  2009-11-05 18:45:04 ---
The Working Group decided to allow external functions to be private, on the
theory that a module need not share how it implements functionality.

This requires no changes to the document.


--
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.