Vladimir is right. If we make a method public people assume it is a public API and start using it, then we are accused of breaking semantic versioning when we change something. This principle is even more important in code like RexToLixTranslator which is a bit messy and which we hope to clean up - or at least evolve - at some point.
That said, if you want something to become a public API, go ahead and make a case for it and we will listen. Julian On Wed, Oct 14, 2015 at 10:27 AM, Vladimir Sitnikov <[email protected]> wrote: >> Is there any technical reasons behind the $subject for 'translate' methods >> in RexToLixTranslater? > > What is your question exactly? > Do you want the methods to be private or public? > > I think the main reason for not-public is for encapsulation reasons: > to reduce diversity of usage kinds, thus to reduce diversity of bug > kinds. > I would not say I like each bit of RexToLixTranslater, however it is > nice to keep interface simple. > > Vladimir
