From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder4.news.weretis.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Thu, 26 Jun 2014 17:25:10 +0200
From: "G.B." <rm-dash-bau-haus@dash.futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Help understanding the benefits of Ada's exception model
References: <dfb783d6-cf59-46f6-bd84-ae92bd392331@googlegroups.com>
 <a7861962-ff0c-4c30-a916-b5c6e2afae01@googlegroups.com>
In-Reply-To: <a7861962-ff0c-4c30-a916-b5c6e2afae01@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <53ac3b56$0$6654$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 26 Jun 2014 17:25:10 CEST
NNTP-Posting-Host: 7b15a97d.newsspool3.arcor-online.net
X-Trace: 
 DXC=[i@fEH6Xe=\HigV@eW57PQMcF=Q^Z^V3X4Fo<]lROoRQ8kF<OcfhCO[9hGMMZkPF?Vnc\616M64>ZLh>_cHTX3j]bVI^3fJdDXT
X-Complaints-To: usenet-abuse@arcor.de
Xref: news.eternal-september.org comp.lang.ada:20618
Date: 2014-06-26T17:25:10+02:00
List-Id: <comp.lang.ada>

On 26.06.14 16:28, Patrick wrote:
> Sorry for answering my own post. I think I have not used the terms unchecked exception and check exceptions properly.  Better terms would be handling exceptions and handling error codes.
>
Right, and the usual answer is that _if_ you want non-local
transfer of control, then checking error codes just won't do.
You'd be using something like setjmp/longjmp in C.
the alternative is to handle error codes all the way up the
call chain. The resulting code is more spaghetti-like and it
will mix both return values and special return values in
the same syntactic structure.

I can't think of a language in use today that does not have
either exception handling, or else some way to check, at compile
time, that none can occur.