| Frank Swarbrick 2007-09-24, 6:56 pm |
| >>> On 9/21/2007 at 10:48 PM, in message
<L81Ji.49884$TK1.22637@fe04.news.easynews.com>, William M.
Klein<wmklein@nospam.netcom.com> wrote:
> "Frank Swarbrick" <Frank.Swarbrick@efirstbank.com> wrote in message
> news:46F4154F.6F0F.0085.0@efirstbank.com...
> <snip>
> times I
> COBOL.
> "try/catch/finally"
>
> One of the "issues" with the '02 Common Exception Handling "model" was
> the
> decision to use DECLARATIVES - as these were already a "part of the
> language"
> for a few exceptions. there is LIMITED control on such things in the
> '02
> Standard by using the
> compiler directing statement to "localize" where detecting exceptions
> occurs.
> The RESUME statement (which will probably be made optional in the next
> revision - if any) has some options for how/where execution resumes (if
> the
> program decides to do so).
>
> I don't know if this helps any - and I certainly think that the basic
> "desing"
> is part of the reason that no compiler vendor has fully implemented it
> (and few
> have implemented it at all). If you care, I believe the model is MOST
> similar
> to that which has (alwasy?) been available with PL/I (or even the EXEC
> CICS
> HANDLE CONDITON). The two designs are NOT identical, but they are more
> similar
> to each other than to newer Try/Catch/Finally type designs.
I'm all for the more generic use of DECLARATIVES as use for a 'catch all'
for exceptions, but it seems like localization would be useful as well.
Ah well. Not like any of this will ever be implemented where it would be
useful to me anyway...
Frank
|