fabi/Snappy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct an inaccuracy in the Snappy format description.

Browse Source 
(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
This commit is contained in:
snappy.mirrorbot@gmail.com
2011-06-04 10:19:05 +00:00
parent f540673740
commit 13c4a449a8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
format_description.txt
View File

@@ -52,7 +52,7 @@ of the literal:
- For literals up to and including 60 bytes in length, the upper - For literals up to and including 60 bytes in length, the upper
six bits of the tag byte contain (len-1). The literal follows six bits of the tag byte contain (len-1). The literal follows
immediately thereafter in the bytestream. 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 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 many bytes are used for the length; 60, 61, 62 or 63 for
1-4 bytes, respectively. The literal itself follows after the 1-4 bytes, respectively. The literal itself follows after the