Merge pull request #5287 from ethereum/docs-update-input-parameters

DOCS: Merge FAQ into docs on multi-dimensional arrays
This commit is contained in:
chriseth 2018-11-26 15:19:55 +01:00 committed by GitHub
commit f1cebed998
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 6 deletions

View File

@ -30,6 +30,16 @@ with two integers, you would use something like::
Function parameters can be used as any other local variable and they can also be assigned to.
.. note::
An :ref:`external function<external-function-calls>` cannot accept a
multi-dimensional array as an input
parameter. This functionality is possible if you enable the new
experimental ``ABIEncoderV2`` feature by adding ``pragma experimental ABIEncoderV2;`` to your source file.
An :ref:`internal function<external-function-calls>` can accept a
multi-dimensional array without enabling the feature.
.. index:: return array, return string, array, string, array of strings, dynamic array, variably sized array, return struct, struct
Return Variables
@ -56,7 +66,7 @@ two integers passed as function parameters, then you use something like::
The names of return variables can be omitted.
Return variables can be used as any other local variable and they
are zero-initialized. If they are not explicitly
are initialized with their :ref:`default value <default-value>` and have that value unless explicitly set.
set, they stay zero value.
You can either explicitly assign to return variables and
@ -122,6 +132,8 @@ the same as the number of return types.
Function Calls
==============
.. _internal-function-calls:
Internal Function Calls
-----------------------
@ -143,6 +155,8 @@ contract can be called internally.
You should still avoid excessive recursion, as every internal function call
uses up at least one stack slot and there are at most 1024 slots available.
.. _external-function-calls:
External Function Calls
-----------------------

View File

@ -269,11 +269,6 @@ to create an independent copy of the storage value in memory.
On the other hand, ``h(x)`` successfully modifies ``x`` because only
a reference and not a copy is passed.
Is it possible to return an array of strings (``string[]``) from a Solidity function?
=====================================================================================
Only when ``pragma experimental "ABIEncoderV2";`` is used.
What does the following strange check do in the Custom Token contract?
======================================================================