From 607f82ce9e9e8ec34f2c042d31bda869368e889b Mon Sep 17 00:00:00 2001 From: Alex Beregszaszi Date: Sat, 15 Oct 2016 22:54:45 +0100 Subject: [PATCH] FAQ: remove visibility section (already explained elsewhere) --- docs/frequently-asked-questions.rst | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index c88c86ed7..36b211fdc 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -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? =====================================================