In order to improve things, make it very clear when encountering and
understanding the purpose of a public method or class, if it is part of
the subsystem's API or not (by improving the javadoc for that method or
class).
Also for every public class that you now change to a lesser visibility,
slap yourself on your left hand and say: "I should have gotten this
right when I introduced the class."!
Otherwise I don't think there is a risk that someone else has used these
classes.
/Linus
> -----Original Message-----
> From: Bob Tarling [mailto:[EMAIL PROTECTED]
> Sent: den 23 augusti 2006 08:06
> To: [email protected]
> Subject: [argouml-dev] Defining the persistence API
>
> All of the persistence classes currently appear to be public. I plan
> to make those that are not called from outside that package become
> package scope. These are helper methods designed to be used internally
> by the other persistence classes. Do I really have to deprecate these
> before changing or can I short cut this?
>
> I'll then review what is left to try and define a more stable API.
>
> Bob.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
