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: When to raise predefined exceptions (was: Ada and the Automotive
 Industry)
Date: 1996/12/22
Message-ID: <dewar.851241406@merv>#1/1
X-Deja-AN: 205409521
references: <mazzanti-0512961053010001@131.114.200.115>
 			<EACHUS.96Dec10195317@spectre.mitre.org>
 			<32B197A6.2781E494@escmail.orl.lmco.com>
 <EACHUS.96Dec17091753@spectre.mitre.org>
 <32BA9772.2781E494@escmail.orl.lmco.com>
 <32BAEE39.773C@velveeta.apdev.cs.mci.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-12-22T00:00:00+00:00
List-Id: <comp.lang.ada>


Jim Rogers said

"I see your point, however it is possible to design away this
problem by handling CE in the subprogram in which it is raised by
raising your new exception.  This way calling subprograms would only
encounter your new exception.  If you use Ada.Exceptions you can
indicate what really happened in the Exception_Information string.
"


You mean Exception_Message here ....