🚀 go-pugleaf

This is a follow up to the UUDECODE program in ST BASIC I posted to this BBS.

Additional notes:

     1. The UUDECODE program does append spaces to the end of the line if it
        thinks they were removed in transit.

     2. The file length (in bytes) is always a multiple of 45. The extra
        bytes are filled with garbage and hopefully ignored. (This is not
        standard UUDECODE.)

     3. This being a BASIC program, it is slow. Typical time, about 1 sec
        per line of coded info (using a ram disk). [about 40 minutes for
        UNITERM, which was 135,000+ bytes before decoding.]

     4. I had trouble UUDECODING the MONST program posted recently here. It
        turns out there were 2 carriage returns at the end of each line.
        Editting with either UEMACS or 1ST WORD fixed the problem (enter
        editor, make no changes except to save the file). The problem was
        probably caused initially by me using KERMIT incorrectly.

I have received several messages from network servers warning me that my
original message was not delivered. If anyone needs a copy, let me know.
Also, if anyone finds any bugs and or helpful fixes, let me know.

Thanks, and good luck!
---Patrick Simon
   PSIMON%PPC.MFENET@LLL-MFE.ARPA
   9-15-86