From 13c4a449a8ea22139c9aa441e8024eebc9dbdf6e Mon Sep 17 00:00:00 2001 From: "snappy.mirrorbot@gmail.com" Date: Sat, 4 Jun 2011 10:19:05 +0000 Subject: [PATCH] Correct an inaccuracy in the Snappy format description. (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 --- format_description.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/format_description.txt b/format_description.txt index 943bfc2..31e717c 100644 --- a/format_description.txt +++ b/format_description.txt @@ -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