Re: Need advice re package organization.

["Randy Brukardt" <randy@rrsoftware.com>]

"Warren W. Gay VE3WWG" <ve3wwg@cogeco.ca> wrote in message
news:7DbWa.1370$qN3.183518@news20.bellglobal.com...

> Agreed that the risk is lower, but it still exists if you place
> the objects (from a library) in the hands of a user.  If you
> are supporting that library, this increases risk of servicing
> calls that should not be your responsibility.

Why would a user be creating child units of the library? That seems dubious
in the first place.

Taking the example of Claw, if you declared a package like
Claw.Dialog.Foobar, you could get access to a lot of Claw internals. But the
only reason for a user to declare such a package is that they needed such
access (hopefully, they're building a new reusable component). In which
case, more hiding is not going to help.

Certainly, anyone who just "with"s Claw.Dialog is not going to get any
private stuff. And, in our experience with a large library given to the
general public, people aren't declaring (grand)children of Claw just so they
can fiddle around with stuff that they don't need. Especially as we spend a
lot of effort keeping the public interfaces stable, but we certainly say
nothing about private stuff. So I view this as a non-problem, especially as
techniques exist to avoid it.

If your users are randomly declaring children, their project has serious
project management problems. It's unlikely that the language can fix these
(or should try).

                Randy.