Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!zehntel!hplabs!sri-unix!BILLW@SRI-KL.ARPA
From: BILLW@SRI-KL.ARPA
Newsgroups: net.micro
Subject: Partity:  Writing better software
Message-ID: <12508@sri-arpa.UUCP>
Date: Wed, 15-Aug-84 04:28:35 EDT
Article-I.D.: sri-arpa.12508
Posted: Wed Aug 15 04:28:35 1984
Date-Received: Sun, 19-Aug-84 02:06:18 EDT
Lines: 16

From:  William Chops Westfield 

By the way, There was an article in the latest issue of "Electronic Design"
on writing "Fault Tolerant Software" that was pretty good.  Some of the
things they recomended included using doubly linked lists instead of
singly linked lists, including checksums in data, checking for out of
range conditions even when fetching operands from memory that should
already be in range, and so on (in addition to more standard schemes
that require some hardware assistance, like watchdog timers).
They were also careful to point out the difference between fault
tolerant software and fail-safe software (the latter includes the
way most systems handle parity errors - you just return the system
to a known state...)

BillW
-------