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,1e4280c6ade7eb23
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: Exception types?
Date: 1998/06/18
Message-ID: <m3ra0mfevl.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 364110071
References: <Pine.BSF.3.96.980608083034.15065A-100000@shell5.ba.best.com>
 <m3hg1vd4lw.fsf@mheaney.ni.net>
 <Pine.BSF.3.96.980609091815.20778A-100000@shell5.ba.best.com>
 <3586FFC0.5FEC1CBC@fiu.edu> <6macfi$hm6$1@platane.wanadoo.fr>
Organization: Network Intensive
Newsgroups: comp.lang.ada
Date: 1998-06-18T00:00:00+00:00
List-Id: <comp.lang.ada>


"Jean-Pierre Rosen" <rosen.adalog@wanadoo.fr> writes:

> Therefore it is clear that *catching* an exception can only be done with
> statically defined exception names. Therefore, the only remaining
> interesting thing that could be done with "exception variables" would be
> raising. But this is now available with the package Ada.Exceptions.
> Therefore, there is no need to add these features to the language.

True, but you gotta admit the syntax for raising an exception with a
message attached is a bit heavy:

   if <I/O failed> then
      Raise_Exception (IO_Error'Identity, "CRC check failed");
   end if;

It just seems hipper to be able to say

   if <I/O Failed> then
      raise IO_Error ("CRC check failed");
   end if;

I'm sure the language design team considered things like this, and am
equally sure they had good reasons to reject it.  Nice to fancy, though,
huh?