Skip to content

Commit

Permalink
Correct an inaccuracy in the Snappy format description.
Browse files Browse the repository at this point in the history
(I stumbled into this when changing the way we decompress literals.) 

R=csilvers

Revision created by MOE tool push_codebase.


git-svn-id: https://snappy.googlecode.com/svn/trunk@43 03e5f5b5-db94-4691-08a0-1a8bf15f6143
  • Loading branch information
snappy.mirrorbot@gmail.com committed Jun 4, 2011
1 parent f540673 commit 13c4a44
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion format_description.txt
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ of the literal:
- For literals up to and including 60 bytes in length, the upper
six bits of the tag byte contain (len-1). The literal follows
immediately thereafter in the bytestream.
- For longer literals, the length is stored after the tag byte,
- For longer literals, the (len-1) value is stored after the tag byte,
little-endian. The upper six bits of the tag byte describe how
many bytes are used for the length; 60, 61, 62 or 63 for
1-4 bytes, respectively. The literal itself follows after the
Expand Down

0 comments on commit 13c4a44

Please sign in to comment.