Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcnc!ncsuvx!ncsugn!emigh
From: emigh@ncsugn.ncsu.edu (Ted H. Emigh)
Newsgroups: comp.unix.wizards,comp.misc,comp.sources.d
Subject: Re: UUDECODE and trailing spaces
Message-ID: <423@ncsugn.ncsu.edu>
Date: Mon, 25-May-87 11:59:12 EDT
Article-I.D.: ncsugn.423
Posted: Mon May 25 11:59:12 1987
Date-Received: Tue, 26-May-87 01:48:34 EDT
References: <924@killer.UUCP>
Reply-To: emigh@ncsugn.UUCP (Ted H. Emigh)
Organization: Genetics, North Carolina State University, Raleigh, NC
Lines: 18
Keywords: a possible solution
Xref: mnetor comp.unix.wizards:2453 comp.misc:586 comp.sources.d:713

In article <924@killer.UUCP> tad@killer.UUCP (Tad Marko) writes:
>In a future
>version of uuencode, why can't the spaces either *always* be guaranteed
>to be there (ie. by being sealed in by a character that always marks
>the end of lines) or make a uudecode that doesn't need them (ie. it
>figures that since this line is short, it needs to be padded)?

In the version of uuencode that I have (taken off the net some months
ago) each line is given a checksum.  This checksum is never a blank
(as far as I can tell), so this problem should never arise with this
version.  In addition, we get a checksum to let us know when the file
the we have has problems.


-- 
Ted H. Emigh, Departments of Genetics & Statistics, NCSU, Raleigh, NC
uucp:     mcnc!ncsugn!emigh		BITNET:	NEMIGH@TUCC
internet: emigh%ncsugn.ncsu.edu     or  @ncsuvx.ncsu.edu:emigh@ncsugn.ncsu.edu