cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify docs around reserved memory byte ranges

Browse Source 
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.
This commit is contained in:
wbt 2018-09-06 13:02:38 -04:00 committed by chriseth
parent cb3a837251
commit bc363a7e3a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/miscellaneous.rst
View File

@ -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)