Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!chinet!nucsrl!gore
From: gore@nucsrl.UUCP
Newsgroups: comp.lang.misc
Subject: Re: Object-Oriented vs. Abstract Data Types
Message-ID: <4000003@nucsrl.UUCP>
Date: Fri, 23-Jan-87 14:43:26 EST
Article-I.D.: nucsrl.4000003
Posted: Fri Jan 23 14:43:26 1987
Date-Received: Sat, 24-Jan-87 23:36:28 EST
References: <1023@cuuxb.UUCP>
Organization: Northwestern Univ., Evanston IL
Lines: 17

> > [...] Basically, the only reason *not* to
> > have dynamic binding is the belief that "it costs too much".
> 
> Not so.  Another reason to avoid dynamic binding is that doing so
> makes it easier to catch certain programming errors early on.
> The earlier an error is caught, the less damage it does.

This is the part that troubles me most about run-time error checking.
In order for an error to be noticed at run time, the program thread
containing the error has to be executed.  This may not happen until
the program had been out in the field for many months (or years...).
The only way to test for such errors it to have a test suite that
executes every single branch in the software.

Jacob Gore
Northwestern University, Computer Science Research Lab
{ihnp4,chinet}!nucsrl!gore