🚀 go-pugleaf

In article <3576@utcsri.UUCP> greg@utcsri.UUCP (Gregory Smith) writes:
>
>This is silly. Broken computers don't give wrong answers. They crash,
>or they log soft errors, or they act flaky. It is almost impossible to
>imagine a hardware fault that would have no visible effect other than
>to make the 'value' (whatever it may be) of the output wrong.
>

	I guess you asked for it ..... here is my war story. At a previous
job our Burroughs 6700 (remember those? they took up a whole room, about as
fast as a 780) had a problem ... one of the people using the stats packages
checked his work by hand (I guess he didn't trust the machine) turns out that
sometimes it was wrong (but always consistantly wrong for the same input data).
It took months to track it down to the MOD instruction that gave wrong answers
only for some input values. Of course the engineer didn't beleive us until we
could give him really hard proof. He said something like


	"This is silly. Broken computers don't give wrong answers"    (:-)




		Paul Campbell
		ucbvax!unisoft!paul