aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorwbt <wbt@users.noreply.github.com>2018-09-07 01:02:38 +0800
committerchriseth <chris@ethereum.org>2018-09-24 22:26:35 +0800
commitbc363a7e3a09217a6f0b72072afb0fbd35f49c97 (patch)
tree86cf57492e038c8bf4fb9c3a88f6af4a505e0231 /docs
parentcb3a837251087001c738cb8f123db231bb00a31d (diff)
downloaddexon-solidity-bc363a7e3a09217a6f0b72072afb0fbd35f49c97.tar.gz
dexon-solidity-bc363a7e3a09217a6f0b72072afb0fbd35f49c97.tar.zst
dexon-solidity-bc363a7e3a09217a6f0b72072afb0fbd35f49c97.zip
Clarify docs around reserved memory byte ranges
Minor documentation issue to improve reading flow as it goes from talking about a specified number of 32-byte slots being reserved to giving numbers which refer to byte ranges within the space of memory resulting from the union of those slots.
Diffstat (limited to 'docs')
-rw-r--r--docs/miscellaneous.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/miscellaneous.rst b/docs/miscellaneous.rst
index de3ab962..5d2819df 100644
--- a/docs/miscellaneous.rst
+++ b/docs/miscellaneous.rst
@@ -64,7 +64,7 @@ The position of ``data[4][9].b`` is at ``keccak256(uint256(9) . keccak256(uint25
Layout in Memory
****************
-Solidity reserves four 32 byte slots:
+Solidity reserves four 32-byte slots, with specific byte ranges (inclusive of endpoints) being used as follows:
- ``0x00`` - ``0x3f`` (64 bytes): scratch space for hashing methods
- ``0x40`` - ``0x5f`` (32 bytes): currently allocated memory size (aka. free memory pointer)