- Oct 03, 2010
-
-
Nathan Froyd authored
-
Nathan Froyd authored
-
Nathan Froyd authored
-
- Sep 30, 2010
-
-
Nathan Froyd authored
-
- Feb 28, 2010
-
-
Nathan Froyd authored
Peculiarly, this bug did not show up in my earlier tests.
-
- Feb 15, 2010
-
-
Nathan Froyd authored
base32, base64, and ascii85 all need to check for particular characters: CONVERTER logic in the decoding functions was misinterpreted for this case. CONVERTER is really for turning elements of the input sequence into integers and was inappropriately being used to try to convert the special characters into integers, which didn't work when decoding octet vectors. For those checks, explicitly check the type of sequence we're decoding from and take the appropriate transformation on the special character.
-
- Feb 14, 2010
-
-
Nathan Froyd authored
-
Nathan Froyd authored
This is more consistent with what Common Lisp already does (e.g. READ-SEQUENCE), as well as being slightly more efficient.
-
- Feb 13, 2010
-
-
Nathan Froyd authored
-
Nathan Froyd authored
-
Nathan Froyd authored
-
Nathan Froyd authored
-
- Jan 30, 2010
-
-
Nathan Froyd authored
Use dummy constructors for the decoding bits, since we're not using the new scheme there yet. base85 tests do not yet pass.
-
Nathan Froyd authored
-
- Jan 25, 2010
-
-
Nathan Froyd authored
That's what I get for attempting to be clever.
-
Nathan Froyd authored
-
Nathan Froyd authored
-
Nathan Froyd authored
-
Nathan Froyd authored
-
- Jan 15, 2010
-
-
Nathan Froyd authored
-
- Nov 13, 2009
-
-
Nathan Froyd authored
-