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,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c5ca2cbae60e9fee
X-Google-Attributes: gid103376,public
From: Robert Dewar <robert_dewar@my-deja.com>
Subject: Re: OO puzzle
Date: 1999/12/23
Message-ID: <83t14p$9ps$1@nnrp1.deja.com>#1/1
X-Deja-AN: 564103753
References: 
 <Pine.A41.3.96-heb-2.07.991222103646.28794B-100000@pluto.mscc.huji.ac.il>
 <386102F6.56CEFA22@averstar.com> <83sq9g$5ml$1@nnrp1.deja.com>
X-Http-Proxy: 1.0 x43.deja.com:80 (Squid/1.1.22) for client 205.232.38.14
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Thu Dec 23 11:30:55 1999 GMT
X-MyDeja-Info: XMYDJUIDrobert_dewar
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I)
Date: 1999-12-23T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <83sq9g$5ml$1@nnrp1.deja.com>,
  Ehud Lamm <mslamm@mscc.huji.ac.il> wrote:
> I assume the importance of catching errors before runtime is
> evident. Now can we do it nicely in this case?

Evident, but not quite so neatly trivial. Run-time errors are
of two kinds:

1. Statements that will always cause an error if executed. Such
errors are bound to get caught by simple coverage testing.

2. Statements where the error is data dependent and there is no
simple guarantee.

Obviously errors in these two classes are a completely different
kettle of fish.


Sent via Deja.com http://www.deja.com/
Before you buy.