cerc-io/solidity
15
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

Merge pull request #4818 from ethereum/clarifyConstructorArgs

Browse Source 
Clarify constructor arguments.
This commit is contained in:
chriseth 2018-08-16 14:54:28 +02:00 committed by GitHub
commit 146e89c2ec
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/miscellaneous.rst
View File

@ -87,11 +87,15 @@ Solidity always places new objects at the free memory pointer and memory is neve
Layout of Call Data Layout of Call Data
******************* *******************
When a Solidity contract is deployed and when it is called from an The input data for a function call is assumed to be in the format defined by the :ref:`ABI
account, the input data is assumed to be in the format in :ref:`the ABI specification <ABI>`. Among others, the ABI specification requires arguments to be padded to multiples of 32
specification <ABI>`. The ABI specification requires arguments to be padded to multiples of 32
bytes. The internal function calls use a different convention. bytes. The internal function calls use a different convention.
Arguments for the constructor of a contract are directly appended at the end of the
contract's code, also in ABI encoding. The constructor will access them through a hard-coded offset, and
not by using the ``codesize`` opcode, since this of course changes when appending
data to the code.
.. index: variable cleanup .. index: variable cleanup