Stowage/go
2
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-11-07 12:11:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix typo in gob docs. They were introduced in revision 3199778baf

Browse source 
"change the encoding of uints...".

R=r
CC=golang-dev
https://golang.org/cl/1436041
This commit is contained in:
Nigel Tao 2010-05-31 17:35:59 -07:00
parent eed5bb3bee
commit c3080418d6
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
src/pkg/gob/encode.go
View file

@ -99,14 +99,14 @@
The low bit is therefore analogous to a sign bit, but making it the complement bit The low bit is therefore analogous to a sign bit, but making it the complement bit
instead guarantees that the largest negative integer is not a special case. For instead guarantees that the largest negative integer is not a special case. For
example, -129=^128=(^256>>1) encodes as (01 82). example, -129=^128=(^256>>1) encodes as (FE 01 01).
Floating-point numbers are always sent as a representation of a float64 value. Floating-point numbers are always sent as a representation of a float64 value.
That value is converted to a uint64 using math.Float64bits. The uint64 is then That value is converted to a uint64 using math.Float64bits. The uint64 is then
byte-reversed and sent as a regular unsigned integer. The byte-reversal means the byte-reversed and sent as a regular unsigned integer. The byte-reversal means the
exponent and high-precision part of the mantissa go first. Since the low bits are exponent and high-precision part of the mantissa go first. Since the low bits are
often zero, this can save encoding bytes. For instance, 17.0 is encoded in only often zero, this can save encoding bytes. For instance, 17.0 is encoded in only
two bytes (40 e2). three bytes (FE 31 40).
Strings and slices of bytes are sent as an unsigned count followed by that many Strings and slices of bytes are sent as an unsigned count followed by that many
uninterpreted bytes of the value. uninterpreted bytes of the value.
@ -123,9 +123,9 @@
order of increasing field number; the deltas are therefore unsigned. The order of increasing field number; the deltas are therefore unsigned. The
initialization for the delta encoding sets the field number to -1, so an unsigned initialization for the delta encoding sets the field number to -1, so an unsigned
integer field 0 with value 7 is transmitted as unsigned delta = 1, unsigned value integer field 0 with value 7 is transmitted as unsigned delta = 1, unsigned value
= 7 or (81 87). Finally, after all the fields have been sent a terminating mark = 7 or (01 0E). Finally, after all the fields have been sent a terminating mark
denotes the end of the struct. That mark is a delta=0 value, which has denotes the end of the struct. That mark is a delta=0 value, which has
representation (80). representation (00).
The representation of types is described below. When a type is defined on a given The representation of types is described below. When a type is defined on a given
connection between an Encoder and Decoder, it is assigned a signed integer type connection between an Encoder and Decoder, it is assigned a signed integer type
@ -198,7 +198,7 @@ package gob
1f // This item (a type descriptor) is 31 bytes long. 1f // This item (a type descriptor) is 31 bytes long.
ff 81 // The negative of the id for the type we're defining, -65. ff 81 // The negative of the id for the type we're defining, -65.
// This is one byte (indicated by FF = ^-1) followed by // This is one byte (indicated by FF = -1) followed by
// ^-65<<1 | 1. The low 1 bit signals to complement the // ^-65<<1 | 1. The low 1 bit signals to complement the
// rest upon receipt. // rest upon receipt.