W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2015

[Bug 29264] [XQ31] XQuery err details as a map

From: <bugzilla@jessica.w3.org>
Date: Fri, 06 Nov 2015 17:02:37 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29264-523-8ie8fJJb0i@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29264

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abel.braaksma@xs4all.nl
            Summary|XQuery err details as a map |[XQ31] XQuery err details
                   |                            |as a map

--- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Note that at some point with XP30 maps were suggested and approved. Later they
were dropped because maps were not ready for inclusion yet (this is why XSLT
and XQuery have the same here, even XSLT has withstood the temptation to turn
the errors into a map, notwithstanding positive support for it). 

Maps have now made it to XP31, whether that means you need an *extra* way of
getting the data of an error, I don't know. If I had the chance, I'd drop the
error vars entirely, a scoped function like current-group() in XSLT but then
current-error() with similar semantics sounds way better, but I'm with Michael
here, I believe we're past our window for new ideas...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 6 November 2015 17:02:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 November 2015 17:02:40 UTC