From b61134bc0a6a904b41522b4e5c9e80874c730cef Mon Sep 17 00:00:00 2001 From: "snappy.mirrorbot@gmail.com" Date: Wed, 5 Oct 2011 12:27:12 +0000 Subject: [PATCH] In the format description, use a clearer example to emphasize that varints are stored in little-endian. Patch from Christian von Roques. R=csilvers git-svn-id: https://snappy.googlecode.com/svn/trunk@51 03e5f5b5-db94-4691-08a0-1a8bf15f6143 --- format_description.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/format_description.txt b/format_description.txt index 43d7a98..20db66c 100644 --- a/format_description.txt +++ b/format_description.txt @@ -1,5 +1,5 @@ Snappy compressed format description -Last revised: 2011-08-09 +Last revised: 2011-10-05 This is not a formal specification, but should suffice to explain most @@ -21,8 +21,8 @@ The stream starts with the uncompressed length (up to a maximum of 2^32 - 1), stored as a little-endian varint. Varints consist of a series of bytes, where the lower 7 bits are data and the upper bit is set iff there are more bytes to be read. In other words, an uncompressed length of 64 would -be stored as 0x40, and an uncompressed length of 2097151 (0x1FFFFF) -would be stored as 0xFF 0xFF 0x7F. +be stored as 0x40, and an uncompressed length of 2097150 (0x1FFFFE) +would be stored as 0xFE 0xFF 0x7F. 2. The compressed stream itself