From 25a693d99c8d9220addf8d9955299feedb4ddb92 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A9ter=20G=C3=B6m=C3=B6ri?= Date: Wed, 9 Sep 2015 12:36:35 +0100 Subject: 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 --- system/doc/efficiency_guide/binaryhandling.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'system') 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 = <>, %% 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 Bin0 or 256, whichever is larger. In this case + size of Bin1 or 256, whichever is larger. In this case it is 256. Line 3 is more interesting. Bin1 has 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. - Line 4. The same applies here. There are 252 bytes left, + Line 4. The same applies here. There are 249 bytes left, so there is no problem storing another 3 bytes. Line 5. Here, something interesting happens. Notice -- cgit v1.2.3