Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!dcl-cs!bath63!pes
From: pes@bath63.ux63.bath.ac.uk (Paul Smee)
Newsgroups: comp.sys.atari.st
Subject: Re: uuencodeded uudecode program is here.
Message-ID: <649@bath63.ux63.bath.ac.uk>
Date: Tue, 9-Dec-86 13:25:28 EST
Article-I.D.: bath63.649
Posted: Tue Dec  9 13:25:28 1986
Date-Received: Wed, 10-Dec-86 11:05:28 EST
References: <861208050928.462912@RADC-MULTICS.ARPA>
Reply-To: pes@ux63.bath.ac.uk (Paul Smee)
Organization: AUCC c/o University of Bath
Lines: 25


  ... Sacrificial offering ...
And, thanks to Rodney Peck for posting it.  As I'd explained to him, the
only way I've got to put things *onto* newsnet is by typing them in, which
didn't feel like a good idea here.

One comment, I have (so far, up to 1.6c) managed to UUDECODE UniTerm with
it as well (on an ST520).  However, I *did* have to CAT the pieces together
on my Multics before porting it to the ST.

Apologise for the fact that the C's a bit tacky, particularly my part of
it.  Twas my first serious thing-to-do in C; and I'm scared to clean it
up now that I know better, lest I might break it.  I've been considering
changing it to use translate table lookup, and to 'know' that the
accent grave is == to a space, since that seems to be a common perversion.

And yes, I'm aware of the chicken-and-egg problem here (UUENCODED UUDECODE)
but suspect that can be gotten around by finding a friend with a U**x or
by using the (or a) BASIC UUDECODE program.

Finally, one note.  Based on conversations over here, it appears that porting
stuff to the ST by UUDECODEing on a mainframe and then binary xfering the
result is quite likely not to work, for reasons which no-one I know of has
worked out.  I've never seen any problems though if you ASCII port to the ST
and then UUDECODE there.