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

FAQ: remove visibility section (already explained elsewhere)

Browse Source
This commit is contained in:
Alex Beregszaszi 2016-10-15 22:54:45 +01:00
parent c6e7475f05
commit 607f82ce9e
1 changed files with 0 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/frequently-asked-questions.rst
View File

@ -144,29 +144,6 @@ from web3 (inside geth or a web application). The main advantage of events
is that they are stored in a special way on the blockchain so that it
is very easy to search for them.
What are the different function visibilities?
=============================================
The visibility specifiers do not only change the visibility but also
the way functions can be called. In general, functions in the
same contract can also be called internally (which is cheaper
and allows for memory types to be passed by reference). This
is done if you just use ``f(1,2)``. If you use ``this.f(1,2)``
or ``otherContract.f(1,2)``, the function is called externally.
Internal function calls have the advantage that you can use
all Solidity types as parameters, but you have to stick to the
simpler ABI types for external calls.
* ``external``: all, only externally
* ``public``: all (this is the default), externally and internally
* ``internal``: only this contract and contracts deriving from it, only internally
* ``private``: only this contract, only internally
Do contract constructors have to be publicly visible?
=====================================================