On 07/22/2011 09:40 AM, mP wrote:
Why does anyone need an impl, whenone can hide implementaitons by
making them package private in the original package. Naturally one
needs a public factory to expose the impls. *.impl packages are nasty
for the simple reason they are still public
... this holds true in plain Java. It's not true with OSGi or the
NetBeans Platform or other component framework.
One simple reason to keep them separate is that when I look at the
classes in a package I want to see in a visually different way what's
public and what's private (yes, sometimes I even split the interface and
the implementatio in two different modules, and that gives plenty of
visual separation, but in many simple cases this is overdoing).
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
