🚀 go-pugleaf

"Josh Fletcher (borland.com)" <jfletcher@borland.com> writes:

In addition to Wilkman's answer:

> interface TENode extends MutableTreeNode, Cloneable
> {
> }
> 
> abstract class AbstractTENode extends DefaultMutableTreeNode implements
> TENode
> {
> }

Since DefaultMutableTreeNode already implements MutableTreeNode, this
is equivalent to

 abstract class AbstractTENode extends DefaultMutableTreeNode implements
 Cloneable
 {
 }

but without the "double interface declaration".

This could be a cause of the debugger field "invisibility": I have
noticed that JBuilder 3's Code Insight does not want to provide
argument lists for methods if a reference is of an interface type.

> 2. In general, it seems that using and abstract class to implement
> another abstract class (the interface) is a little wierd.  It's as if he
> is trying to get multiple inheritance or something.  Am I wrong here?

No, it's MI of interface, but they probably want to "force"
subclassing. A class declared abstract does not need to have abstract
methods, but a class having abstract methods must be declared as one.