Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!nuchat!steve
From: steve@nuchat.sccsi.com (Steve Nuchia)
Newsgroups: comp.unix.sysv386
Subject: Re: The INfamous inode bug
Message-ID: <1991Jan12.025119.27665@nuchat.sccsi.com>
Date: 12 Jan 91 02:51:19 GMT
References: <5685@rsiatl.Dixie.Com> <53@esacs.UUCP> <1991Jan10.161022.3360@ism.isc.com>
Organization: South Coast Computing Services, Inc.  Houston
Lines: 19

In article <1991Jan10.161022.3360@ism.isc.com> support@bomber.ism.isc.com (Support Account) writes:
>Code was added/fixed in V2.2 of Interactive Unix which resolved
>all the instances of the inode problem Interactive could test
>internally. Recently, another situation which generates the bug
>was discovered, which was not tested for, and which is being fixed.

Wouldn't it have been easier to have proved the revised code the
first time?  Simple little resource managers like that can be proved
in a half hour or so, and then you don't embarass yourself.

(No, I don't always prove my code the first time.  But if there is
a second time you can bet there won't be a third time.)

Testing for correctness.  Sheesh.
-- 
Steve Nuchia	      South Coast Computing Services      (713) 964-2462
	"Could we find tools that would teach their own use,
	 we should have discovered something truly beyond price."
		Socrates, in Plato's Republic