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,a3ca574fc2007430
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Ada and Automotive Industry
Date: 1996/12/22
Message-ID: <dewar.851268871@merv>#1/1
X-Deja-AN: 205449783
references: <mazzanti-0512961053010001@131.114.200.115> <dewar.850626633@merv>
 <E2L8Ap.HCs@world.std.com> <dewar.850929677@merv> <E2MvrB.Ip7@world.std.com>
 <32B8AF89.CA@lmtas.lmco.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-12-22T00:00:00+00:00
List-Id: <comp.lang.ada>


Ken says

"Actually, I like to raise Program_Error when this happens. Its' roughly
equivalent to the "WTF?" message we used to generate in our FORTRAN
tools
when we reached a condition in the program that "shouldn't happen.""



I prefer to make the distinction that the RM makes. Program_Error is raised
for logic errors in your program, which should never occur. Constraint_Error
is raised for an incorrect value that is outside the domain or range of
a basic operation.

It is of course true that this is not a well defined sharp line!