Re: [TCLCORE] Rationale for non-strict [binary decode]

[Pat T. <pat...@us...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Firstly - I do this stuff in my spare time. That would be time that I'm
not involved with family or work - so if it takes a couple of days to
get a response that doesnt mean I never answer your mails.

I did the uuencoding purely to facilitate the tcllib implementation
which handles the outer wrapping "begin ... end" and the line length
stuff separately from the encoding of the data. So its been done as a
straight C replacement for the inner part of tcllibs implementation. If
everyone wants to complain about it we can just throw it away entirely -
the only important encodings are base64 and hex and maybe ascii85 which
isn't done but should be soon as its becoming used in more protocols now.

The fix for just ignoring whitespace looks ok to me. I dont remember if
there was a particular reason for ignoring any invalid characters and in
the absence of specific tests or comments aboout the issue we may assume
it is an accident. Ignoring whitespace is definately required.

Pat Thoyts
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBSUbJ0GB90JXwhOSJAQLnDwP/Ys3fHqLxIeOO51Tmwhlv7CQhc2WNtu+C
jZ9ryoOgxuRQwFyn8+5aMY6EYX7tEJCxP8pSnQbBHSV6hWA097wz/aNyqaM/2i5D
5r3fK/mqhDl9XOE1zxXWaN1fawrIZpq2IdNgTpxUtGFKxwtGVEGz3AndokMA+3Mm
hByV4bLTg8U=
=S+rd
-----END PGP SIGNATURE-----