Re: Separate interface and implemenation problem..

Patricia Shanahan wrote:


You get a lot of that by declaring the interface itself package-
private. The only limitation is that it's an all-or-nothing
proposition. Every method in the interface is accessible only to the
package, or every method is accessible to the public; you can't mix
the two. However, in ten years I've never come up with a need to mix
the two.

Mark Space wrote:


Static methods go against the point of interfaces, since static
methods cannot be inherited. You get everything you need from static
methods in a utility (usually non-instantiable) class anyway.

Protected methods exist to allow implementation inheritance. There is
no real need for interfaces to have them. You can get nearly all of
what you might want from protected interface methods by using a
protected nested interface.

In practice, I have yet to find that interface methods are public to
be a limiting factor.


--
Lew