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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fee8802cc3d8334d
X-Google-Attributes: gid103376,public
From: Hyman Rosen <hymie@prolifics.com>
Subject: Re: Ada and Java. different behaviour. casting long to int problem.
Date: 1999/06/17
Message-ID: <t7bteed21s.fsf@calumny.jyacc.com>#1/1
X-Deja-AN: 490792550
Sender: hymie@calumny.jyacc.com
References: <7jt2c0$vrb@drn.newsguy.com> <f92d7yyweva.fsf@eng.sun.com>
 <7k57vb$1ipf@drn.newsguy.com> <3766650F.705125B7@pwfl.com>
 <7k64t7$igo$1@its.hooked.net> <7k689a$ci2@drn.newsguy.com>
 <3766C842.E1EAB60A@pwfl.com> <3766D1CC.D712895E@itools.symantec.com>
 <7k8nn5$qcb$1@its.hooked.net> <3767E8A2.EF1A0570@itools.symantec.com>
 <7k8tv3$3gm@drn.newsguy.com> <t7so7rdd1u.fsf@calumny.jyacc.com>
 <3769506F.157411C0@mitre.org>
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@panix.com
X-Trace: news.panix.com 929649885 24928 209.49.126.226 (17 Jun 1999 20:04:45
 GMT)
Organization: PANIX Public Access Internet and UNIX, NYC
Mime-Version: 1.0
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3
NNTP-Posting-Date: 17 Jun 1999 20:04:45 GMT
Newsgroups: comp.lang.ada
Date: 1999-06-17T20:04:45+00:00
List-Id: <comp.lang.ada>

"Robert I. Eachus" <eachus@mitre.org> writes:
>     It may be time again to point out that that the software behaved
> exactly as it was intended to behave.

Yes, but the rocket blew up! C programmers will make the same claim on
wraparound arithmetic - the program behaves exactly as intended, and
if you suspect and don't want wraparound, you need to explicitly
check.

All I'm saying is that exceptions are better than wraparound only in
the test/debug environment. Out in the field, especially when the
software must work the first time, exceptions are probably going to be
more harmful than wraparound, because the former causes a large part
of the code to abruptly abort, while the latter causes a local
error. In many cases, the local error just causes a glitch but the
system as a whole can continue working.