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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, TO_MALFORMED autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,631686271a29a357,start X-Google-Attributes: gid103376,public From: John Cupak Subject: Common Error/Exception Handler Date: 1996/04/19 Message-ID: <4l8d5i$31g@news.sanders.lockheed.com>#1/1 X-Deja-AN: 150388292 to: jcupak content-type: text/plain; charset=us-ascii organization: Lockheed Martin / Sanders x-url: news:comp.lang.ada?ALL mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 1.1N (X11; I; SunOS 5.3 sun4m) Date: 1996-04-19T00:00:00+00:00 List-Id: I have observed that non-Ada programmers tend to create a "constant" error number header file or package, and then use that constant to write/display the corresponding error message. Ada programmers, however, tend to use "packaged" exceptions, raise the exception where/when appropriate, and "handle" the exception in an exception handler. Wouldn't it be possible with the Ada 95 exception mechanisms to create a package of standard exceptions and a common error message procedure, import/rename the exceptions where appropriate, and let the common error message procedure take care of the details? Inquiring minds want to know! -- John J. Cupak, Jr., CCP Internet : jcupak@isd99.sanders.lockheed.com Lockheed Sanders, Inc. Lockheed LAN : jcupak@mailgw.sanders.lockheed.com 95 Canal Street/MER15-2403 Lockheed DECNet: NHQVAX::CUPAK Nashua, NH 03061-0868 Work Telephone : 603 885-2142 FAX: 603 885-1480