On 17/08/11 13:06, Dan Allen wrote:
On Tue, Aug 16, 2011 at 23:05, Dan Allen <dan.j.allen(a)gmail.com
On Tue, Aug 16, 2011 at 22:57, Shane Bryzak <sbryzak(a)redhat.com
Of course, but we break that rule. Solder is one example,
there's multiple utility classes in the implementation that
are required to compile other modules.
I consider that a bug (or a work in progress, depending on how you
look at it).
An API is an API. If it's an "internal API", then perhaps it should be
an SPI. Under no circumstances should we be depending on
implementation classes between modules. Otherwise, we are changing the
definition of an implementation.
We agree on this, and as far as I know (besides Solder) we conform to
this throughout all the modules.
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597