On Mon, Aug 11, 2008 at 01:58:59PM +0200, Dirk Stöcker wrote: > > When we're at it, I'm not sure the way josm is written makes it any easier > > to work with the code. Using accessors is the standard way every java > > programmer > > understands and the code clutter is not much of an argument. > I do not like these either, but on the other side I also would not fix > these without a good reason. Making elements private and fixing the > sources to work with that is no big issue, but starting with current code > I would do so only in cases, where encapsulation really brings benefit. > Not for the general purpose of clean style.
the main benefit of encapsulation is to make code more flexible for refactoring, internal changes, performance optimization through implementation hiding in case of modular software like josm with plugins is encapsulation a must for development and has not only something to do with clean style of code refactoring and cleanups in an early phase of project are not so expensive and time-consuming like in a big grown old project. sometime it is to late to make big changes... best regards chr _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
