You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Functions annotations in XQuery have become a popular feature to attach vendor-specific information (for unit testing, locking, RESTXQ, etc.) to functions.
Annotation values are limited to literals, though. It would often be helpful to supply boolean values, but we don’t have literals for that in the language.
There's a minor problem with this if the default function namespace isn't "fn". I propose tackling that simply by saying that within the Annotation, the default function namespace IS "fn", regardless what it might be outside.
There's a minor problem with this if the default function namespace isn't "fn". I propose tackling that simply by saying that within the Annotation, the default function namespace IS "fn", regardless what it might be outside.
Good point. +1.
I wasn't sure if we should also allow fn:true() and fn:false(). I eventually omitted those in order to minimize hard-coded string handling.
Functions annotations in XQuery have become a popular feature to attach vendor-specific information (for unit testing, locking, RESTXQ, etc.) to functions.
Annotation values are limited to literals, though. It would often be helpful to supply boolean values, but we don’t have literals for that in the language.
I suggest enhancing the existing grammar…
…and allowing the strings
false()
andtrue()
as values:The suggestion is upward compatible if we should decide later on that we want to allow arbitrary expressions for annotation values.
The text was updated successfully, but these errors were encountered: