Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!brl-adm!brl-smoke!abc
From: abc@brl-smoke.ARPA (Brint Cooper )
Newsgroups: net.crypt
Subject: Re: Decryption of corrupted files...
Message-ID: <853@brl-smoke.ARPA>
Date: Wed, 14-May-86 20:47:25 EDT
Article-I.D.: brl-smok.853
Posted: Wed May 14 20:47:25 1986
Date-Received: Sun, 25-May-86 15:20:59 EDT
References: <60@rtgvax.UUCP> <757@hoptoad.uucp> <13619@ucbvax.BERKELEY.EDU> <529@brl-smoke.ARPA>
Reply-To: abc@brl-smoke.UUCP (Brint Cooper (SECAD/CSMB) <abc>)
Organization: Ballistic Research Lab (BRL)
Lines: 25

Unfortunately (or perhaps fortunately for those in the business),
'simple error-correcting codes' fall into two classes:  powerful codes
(correct many error patterns) that severely impede the rate of
information flow and weak codes that do not.  Error control is not yet a
'handbook' science.

Brint

In article <529@brl-smoke.ARPA> gwyn@brl.ARPA writes:
>In article <13619@ucbvax.BERKELEY.EDU> desj@brahms.UUCP (David desJardins) writes:
>>...  There
>>seems to be a need for a book on "Error Correcting Codes for Programmers,"
>>which would describe how to implement some simple error-correcting codes,
>>but I don't know of any such book....
>
>Richard Hamming wrote such a book; it was aimed at practicing
>engineers rather than theoreticians.  I forget its title, but
>it was something obvious.  Wish I had a copy.


-- 
Brint Cooper

	 ARPA:  abc@brl-bmd.arpa
	 UUCP:  ...{seismo,unc,decvax,cbosgd}!brl-bmd!abc