On Sun, 10 Oct 2004, Tim Jenness wrote:
> > It looks like Alan linked the JNIKAPPA stuff against -lkappa -lkapview
> > -lkapsub, these look to be intermediate build products for kappa that
> > are buried in places like fairly far down the new build tree under the
> > new scheme, e.g. /h/jini/checkout/applications/kappa/libkappa/.libs
>
> This kind of implies that every single JNI java version has to link
> against every private intemrediate library. That does not sound like a
> very extensible plan. Things would be a little easier if we could install
> a single library per monolith [then it becomes part of the public
> interface] but having to install thinkg like libkapsub does not sound
> good.
Increasing the size of a package's public interface carries with it
substantial increases in the maintenance burden, at least notionally.
As a package developer, the smaller my public interface is, the
happier I am, since I don't have to worry about breaking anything
outside if I need to do some refactoring or other jigging around
with existing routines. This may be exactly what you mean by
"does not sound good" above, I just wanted to make it explicit.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|