There's nothing in the JLS by that name however, section 4.5 Parameterized
Types, might be close to what I'm looking for.
Even in a single inheritance system, resolving methods and types is a
multi-dimensional process.
I still say that by not allowing private inner classes, resolving this issue
would be much easier (or providing the access methods in the parent class of
the private internal class would work also ... calling getChildren() really is
a dependency on the underlying classes implementation which I really don't
understand why is declared private and not accessible. There has to be a good
reason otherwise it should be changed or eliminated [get rid of inner classes]).
On Tuesday, January 16, 2018, 7:21:32 AM CST, dalibor topic
<[email protected]> wrote:
On 16.01.2018 14:08, jeffrey kutcher wrote> Is there official
documentation explaining the method resolution process somewhere?
I'd suggest taking a look at the Java Language specification and JVM
specification for details.
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
