From bc363a7e3a09217a6f0b72072afb0fbd35f49c97 Mon Sep 17 00:00:00 2001 From: wbt Date: Thu, 6 Sep 2018 13:02:38 -0400 Subject: 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. --- docs/miscellaneous.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') 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) -- cgit v1.2.3