From 1f4d4231e1071f7d1ae3955ac6b1cec3addf3775 Mon Sep 17 00:00:00 2001 From: Xevion Date: Mon, 2 Mar 2020 21:40:51 -0600 Subject: [PATCH] update origin class call explanation fully --- study/STUDY.MD | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/study/STUDY.MD b/study/STUDY.MD index 254b0ed..0d6dfe1 100644 --- a/study/STUDY.MD +++ b/study/STUDY.MD @@ -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 [RemoveEvenIntegers on repl.it](https://repl.it/@Xevion/RemoveEvenIntegers)