aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPéter Gömöri <[email protected]>2015-09-09 12:36:35 +0100
committerPéter Gömöri <[email protected]>2015-09-09 12:36:35 +0100
commit25a693d99c8d9220addf8d9955299feedb4ddb92 (patch)
tree67e938f7a1d41df5deb189ce4a144ac717b7b961
parentbfdc9f97f1738d072d09b98a8980b0b59639db0b (diff)
downloadotp-25a693d99c8d9220addf8d9955299feedb4ddb92.tar.gz
otp-25a693d99c8d9220addf8d9955299feedb4ddb92.tar.bz2
otp-25a693d99c8d9220addf8d9955299feedb4ddb92.zip
Very minor fixes to binary handling documentation
- at appending when allocating new binary object its size will be double (the old size + size of data to be appended) not just double the old size - correct some unused byte counts
-rw-r--r--system/doc/efficiency_guide/binaryhandling.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/system/doc/efficiency_guide/binaryhandling.xml b/system/doc/efficiency_guide/binaryhandling.xml
index 51f8c4ebf0..0964b759d8 100644
--- a/system/doc/efficiency_guide/binaryhandling.xml
+++ b/system/doc/efficiency_guide/binaryhandling.xml
@@ -190,15 +190,15 @@ Bin4 = <<Bin1/binary,17>>, %% 5 !!!
its size set to the size of the data stored in the binary, while
the binary object has extra space allocated.
The size of the binary object is either twice the
- size of <c>Bin0</c> or 256, whichever is larger. In this case
+ size of <c>Bin1</c> or 256, whichever is larger. In this case
it is 256.</item>
<item>Line 3 is more interesting.
<c>Bin1</c> <em>has</em> been used in an append operation,
- and it has 255 bytes of unused storage at the end, so the 3 new
+ and it has 252 bytes of unused storage at the end, so the 3 new
bytes are stored there.</item>
- <item>Line 4. The same applies here. There are 252 bytes left,
+ <item>Line 4. The same applies here. There are 249 bytes left,
so there is no problem storing another 3 bytes.</item>
<item>Line 5. Here, something <em>interesting</em> happens. Notice