-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing Functions: Empty input #1193
Comments
ChristianGruen
added
XQFO
An issue related to Functions and Operators
Editorial
Minor typos, wording clarifications, example fixes, etc.
labels
May 7, 2024
Generally the specs are a pretty inconsistent mess as regards handling of empty sequence on input; it goes well beyond the parse-XX functions. |
In the particular case, it seems that all pre-4.0 functions allow empty sequences, whereas only some of the new functions do. But it’s true, when cleaning this up we should probably consider the complete function set. |
See also #748 |
ChristianGruen
added a commit
to ChristianGruen/qtspecs
that referenced
this issue
May 21, 2024
ChristianGruen
added a commit
to ChristianGruen/qtspecs
that referenced
this issue
May 28, 2024
ChristianGruen
added a commit
to qt4cg/qt4tests
that referenced
this issue
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was asked why some of the parsing functions allow empty input and others don’t:
fn:parse-integer
xs:string
fn:parse-uri
xs:string
fn:parse-ietf-date
xs:string?
fn:parse-QName
xs:string
fn:parse-xml
xs:string?
fn:parse-xml-fragment
xs:string?
fn:parse-html
(xs:string | xs:hexBinary | xs:base64Binary)?
fn:parse-json
xs:string?
fn:parse-csv
xs:string?
I would assume there is no rationale behind this, and that we should always allow empty input.
The text was updated successfully, but these errors were encountered: