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: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Exception types?
Date: 1998/06/21
Message-ID: <dewar.898438896@merv>#1/1
X-Deja-AN: 364717358
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>
 <3584F47B.3ADF7442@elca-matrix.ch>
 <Pine.BSF.3.96.980615092313.16733A-100000@shell5.ba.best.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 898438961 16107 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-06-21T00:00:00+00:00
List-Id: <comp.lang.ada>


Mats said

<<My proposal is to add parameters to exceptions, as in Modula-3 (and in Ada 95,
with the IMO ridiculous limitation to strings of 200 characters).
>>


I think this limitation is quite reasonable, given the intended use, which
is simply to pass a short identifying message along. It is of course trivial
to eliminate this limitation in an implementation, but only at the expense
of implicit heap use, which is generally undesirable.

(especially if the exception in question is Storage_Error!)