- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 Nov 2015 17:02:37 +0000
- To: public-qt-comments@w3.org
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