posted 19 years ago
Is this "mini-pattern" generally known? It allows you to create an interface that can be used but not implemented outside of its package.
Outside of package p, you can work with objects of interface I, but the reference to p.Private means you won't be allowed to compile a class that tries to implement it.
It's Monday morning, so I may be forgetting a painfully obvious usage, but I was just wondering if anybody has seen an application of this in the wild.