xevion/contest
1
0
Fork 0
mirror of https://github.com/Xevion/contest.git synced 2025-12-10 14:06:52 -06:00
Code Issues Packages Projects Releases Wiki Activity

update origin class call explanation fully

Browse Source
This commit is contained in:
Xevion
2020-03-02 21:40:51 -06:00
parent e8cf1f4735
commit 1f4d4231e1
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
study/STUDY.MD
View File

@@ -453,6 +453,12 @@ B() {
} }
``` ```
Once you understand this, another half of the problem is unlocked, but here, you're still not out of the water yet. Despite the class `A` constructor calling `method()` from it's view in class `A`, it will in fact actually call the `method()` at class `B`.
Methods called at any level, unless explicit called using `super.method()`, methods will always refer to methods found at the origin class (by this, I mean, it will always call class `B` methods).
*Some more testing is order to see how variables, super() and more interact when called through a super constructor, as well as interaction*
### List.remove() Element Shifting ### List.remove() Element Shifting
[RemoveEvenIntegers on repl.it](https://repl.it/@Xevion/RemoveEvenIntegers) [RemoveEvenIntegers on repl.it](https://repl.it/@Xevion/RemoveEvenIntegers)