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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 Apr 2011 16:41:51 +0000
To: public-qt-comments@w3.org
Message-Id: <E1QElKh-000746-Rl@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11792

Jonathan Robie <jonathan.robie@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com> 2011-04-26 16:41:50 UTC ---
In today's telcon, we did not achieve consensus to change the bracket
conventions.

We did achieve consensus to eliminate the CatchVars as follows:

CatchClause     ::=     "catch" CatchErrorList CatchVars? "{" Expr "}"
 =>
CatchClause     ::=     "catch" CatchErrorList "{" Expr "}"

Implicitly define these variables within the scope of a catch clause:

 $err:code
 $err:description
 $err:value

Also implicitly define these variables within the scope of a catch clause -
implementations that do not provide a value for these variables must bind them
to the empty sequence:

 $err:module
 $err:line-number
 $err:column-number

These variables have the same meaning as in XSLT - see
http://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview-diff.html#try-catch

-- 
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, 26 April 2011 16:41:53 UTC

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