W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2011

[Bug 11792] lack of syntactic symmetry between the control flow expressions

From: <bugzilla@jessica.w3.org>
Date: Tue, 18 Jan 2011 17:28:39 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PfFMF-0001Rd-RQ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11792

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> 2011-01-18 17:28:39 UTC ---
Tricky - changing either switch or try/catch to be more like the other will at
the same time make it less like the equivalent construct in the C/Java family
of languages.

The parentheses-versus-curlies problem in XQuery is very real. I've never
understood why validate{} isn't a validate() function, and the distinction
between unordered{} and unordered() is so subtle I doubt many WG members could
explain it without first checking the spec (especially as no-one ever uses
either...). Unfortunately, I think it's too late to fix this, and it's hard to
see how to add new constructs without perpetuating the arbitrariness of it all.
Certainly, changing try() to use parenthesis rather than curlies would make it
more like some things and less like others, without giving any overall
improvement in consistency.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 18 January 2011 17:28:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC