7864 2009-10-09 21:31:51 +0000 [XQuery 1.1] Unclear whether both user-defined and external functions can be both public and private 2009-11-05 18:45:04 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Working drafts All All RESOLVED FIXED P2 normal --- 1 jim.melton jonathan.robie john.snelson public-qt-comments oldest_to_newest 28182 0 jim.melton 2009-10-09 21:31:51 +0000 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. 28278 1 john.snelson 2009-10-12 20:17:50 +0000 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. 29351 2 jonathan.robie 2009-11-05 18:45:04 +0000 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.