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,820de86ed0dafb8a
X-Google-Attributes: gid103376,public
From: Hyman Rosen <hymie@prolifics.com>
Subject: Re: Help Me Please :)
Date: 2000/03/27
Message-ID: <t7u2hrdhnu.fsf@calumny.jyacc.com>#1/1
X-Deja-AN: 603205254
Sender: hymie@calumny.jyacc.com
References: <tgg0u8cb6a.fsf@mercury.rus.uni-stuttgart.de>
 <lJSv4.1648$im1.34999@news.pacbell.net>
 <89rlvr$gn9$1@nntp3.atl.mindspring.net> <wccog8dqvk6.fsf@world.std.com>
 <38D8A607.F61F0FFF@mail.com> <wccya74m18e.fsf@world.std.com>
X-Complaints-To: abuse@panix.com
X-Trace: news.panix.com 954205758 23029 209.49.126.226 (28 Mar 2000 01:09:18
 GMT)
Organization: PANIX Public Access Internet and UNIX, NYC
NNTP-Posting-Date: 28 Mar 2000 01:09:18 GMT
Newsgroups: comp.lang.ada
Date: 2000-03-28T01:09:18+00:00
List-Id: <comp.lang.ada>

Robert A Duff <bobduff@world.std.com> writes:
> The "raises set" of a procedure defines what exceptions it can raise.
> The problem is that this rule is checked at run time.  Java is closer to
> the right solution -- it checks that rule at compile time.  However,
> Java suffers from the "cry wolf" problem.  I think it's possible to
> avoid the "cry wolf" problem, and still do most of that checking at
> compile time.

Most people on comp.lang.c++.moderated have concluded that C++ throw
specifications are useless, except for the throw() spec which says
that a function will throw no exceptions at all. It would be interesting
to see a design which works well.