On 03/19/2013 12:36:20 PM, Erich Plondke wrote:
Attached: updated uuencode/uudecode toys, and tests for both.
Query: for uuencode-traditional, is the blank line at the end required?
Posix doesn't seem to require it, is this a workaround for known bugs
in other uudecode implementations?
Rob
Attached: updated uuencode/uudecode toys, and tests for both.
/* uudecode.c - uudecode / base64 decode
*
* Copyright 2013 Erich Plondke
*
* See http://pubs.opengroup.org/onlinepubs/9699919799/utilities/uudecode.html
USE_UUENCODE(NEWTOY(uudecode, ">2o:", TOYFLAG_USR|TOYFLAG_BIN))
config UUDEC
Hi Rob,
Having a look at Erich's, he has made better use of the toybox
'intrinsic' functions, and he has both encode/decode, so definitely go
with his. I had a test script which essentially compared the output of
mine to the output of the system uuencode, but it wasn't in
scripts/test/*.test, it wa
On 03/14/2013 09:04:18 PM, Erich Plondke wrote:
Looks like I might be a bit late on this browsing the archives... but
uuencode and uudecode implementations are attached.
Both passed basic tests. Support both base64 and traditional format.
Also, I needed to put parens around min/max, but I thin
Looks like I might be a bit late on this browsing the archives... but
uuencode and uudecode implementations are attached.
Both passed basic tests. Support both base64 and traditional format.
Also, I needed to put parens around min/max, but I think a better
option was presented that didn't have
