@UUENCODE and @YENCODE each write a filename to the header line. But it's the wrong filename -- they write the output filename where they should be saving the input filename. This is does not cause a problem for @UUDECODE and @YDECODE, which take the output filename as a parameter. But it will confuse external decoders which expect to use the filename from the header. ("I can't open that file for writing; some smurfhole has it open for reading!")
Also, @YDECODE fails with a spurious CRC error if the checksum in the footer line is immediately followed by a carriage return or line feed. A space or EOF is okay.
Also, @YDECODE fails with a spurious CRC error if the checksum in the footer line is immediately followed by a carriage return or line feed. A space or EOF is okay.
