What's the deal with Java's public fields?
- by Annan
I've been reading two articles (1)(2) on javaworld.com about how all class fields should be private and getter/setter methods are just as bad. An object should act on the data it has rather than allowing access to it.
I'm currently working on a University assignment for Connect Four. In designing the program the Agents playing the Game need access to the Board's state (so they can decide what to move). They also need to pass this move to the Game so it can validate it as a legal move. And during deciding what to move pieces are grouped into Threats with a start and end Points.
Board, Threat and Point objects don't really do anything. They are just there to store related data that can be accessed in a human readable way.
At the start of design I was representing Points on the board as two element int arrays, however that got annoying when creating points or referencing components of them.
So, the class:
public class Point {
public int x;
public int y;
public Point(int x, int y){
this.x = x;
this.y = y;
}
}
Perfect in every way I can think of. Except it breaks every rule I've learned. Have I sinned?
