On Mon, 21 Mar 2022 18:53:20 GMT, Pavel Rappo <pra...@openjdk.org> wrote:
>> Yes, my criticism was about the use of the word "tree" in this case. While I >> agree that this is not the primary use you are trying to eliminate (i.e. >> HtmlTree-like trees) it nevertheless is misleading to describe the >> superclasses of a class as forming a tree, since they form just a single >> branch of any tree. > > Does your comment mean that we should similarly refine (later) the term > "Inheritance Tree"? > > To make sure we're on the same page, that method (whose doc comment we are > talking about) is in charge of producing a small tree-like diagram you can > see on the top of a class page. For example, for java.util.ArrayList that > diagram looks like this: > > > java.lang.Object > java.util.AbstractCollection<E> > java.util.AbstractList<E> > java.util.ArrayList<E> Is there a suitable term we could use to describe this _ancestry_ information? We are specifically interested in a superclass-subclass chain that connects a class in question with java.lang.Object. ------------- PR: https://git.openjdk.java.net/jdk/pull/7843
