RE: "external function" vs "implementation-defined function"

I did not change the definition for external function, but it probably needs to be changed. Here is the text from the CR, which says that implementation-defined functions are a kind of external function in the sentence immediately after the definition:

[Definition: External functions are functions that are implemented outside the query environment.] For example, an XQuery implementation might provide a set of external functions in addition to the core function library described in [XQuery and XPath Functions and Operators 3.1]. External functions are identified by the keyword external. 

If you believe that, then at least some functions provided by the implementation (I assume those must be implementation-defined functions) are implemented outside the query environment.

I think your suggestion is a good one, implementation-defined functions should be a distinct category, disjoint from external functions.  I would suggest we replace the above definition with the following definition:

XQuery:

[Definition: External functions are functions that are neither *built-in functions* nor *implementation-defined functions".] External functions are identified by the keyword external. 

XPath:

[Definition: External functions are functions that are neither *built-in functions* nor *host language functions".] External functions are identified by the keyword external. 

Let's discuss in today's call.

Jonathan

Received on Tuesday, 9 February 2016 15:37:03 UTC