Timeline for Usage of memory, storage and stack areas in EVM
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:58 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 9, 2019 at 18:41 | comment | added | Garen Vartanian | Given that users are limited to 16 total arguments or variables per function - function arguments, return values, and local variables - that tells me that the docs don't reveal the whole story. Even if function arguments are copied into memory, they must be pushed into the stack. The opposite seems to hold true for complex local variable declarations: they can be declared as copied in memory, but I suspect a pointer to the data is placed in stack as well. To the OP, you can't decide for the most part where the data will be stored, unless you can confidently use the assembly code commands. | |
| May 11, 2018 at 18:33 | comment | added | hqt | Can you explain for me when should we use stack and memory. thanks | |
| Jan 31, 2018 at 2:52 | comment | added | William Entriken |
Could you also please explain dynamic arrays bytes[] and where that is stored.
|
|
| Aug 5, 2017 at 10:05 | comment | added | benjaminion | It's not straightforward - it depends where and how you declare it. More info is here: solidity.readthedocs.io/en/develop/… - read through the whole section. | |
| Aug 5, 2017 at 9:39 | comment | added | Abhishek | Thanks for the valuable information. Can you please clerify, if we define a variable as "uint256 x", by deailt it would be storage, memory or stack? | |
| Aug 5, 2017 at 9:36 | vote | accept | Abhishek | ||
| Aug 5, 2017 at 7:07 | history | edited | benjaminion | CC BY-SA 3.0 |
Extra info.
|
| Aug 5, 2017 at 7:01 | history | answered | benjaminion | CC BY-SA 3.0 |