aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2018-01-24 22:38:17 +0800
committerGitHub <noreply@github.com>2018-01-24 22:38:17 +0800
commit513c771e2cbe9037db6f19f2a106e6c309c0d48a (patch)
tree9d7211edcd2b1c430b140c075a480b03ac2e3a8d
parentb177352a874d878e1ae4a31098111086ac7164d2 (diff)
parent4f753233f7b460504a007d94886ab34641ba86ca (diff)
downloaddexon-solidity-513c771e2cbe9037db6f19f2a106e6c309c0d48a.tar.gz
dexon-solidity-513c771e2cbe9037db6f19f2a106e6c309c0d48a.tar.zst
dexon-solidity-513c771e2cbe9037db6f19f2a106e6c309c0d48a.zip
Merge pull request #3433 from ZoOgY-DoOgY/patch-1
Inheritance, "super" and DDD
-rw-r--r--docs/contracts.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/contracts.rst b/docs/contracts.rst
index 273ea43a..a8ea8378 100644
--- a/docs/contracts.rst
+++ b/docs/contracts.rst
@@ -942,12 +942,12 @@ derived override, but this function will bypass
contract Final is Base1, Base2 {
}
-If ``Base1`` calls a function of ``super``, it does not simply
+If ``Base2`` calls a function of ``super``, it does not simply
call this function on one of its base contracts. Rather, it
calls this function on the next base contract in the final
-inheritance graph, so it will call ``Base2.kill()`` (note that
+inheritance graph, so it will call ``Base1.kill()`` (note that
the final inheritance sequence is -- starting with the most
-derived contract: Final, Base1, Base2, mortal, owned).
+derived contract: Final, Base2, Base1, mortal, owned).
The actual function that is called when using super is
not known in the context of the class where it is used,
although its type is known. This is similar for ordinary