Coding Standards

[erikd]

The field is an implementation details, the getter is the API.
If you let the caller to use directly the field you can't rely on an implementation changes without to refactor all usages.

I take by example, if you want to change your implementation for a precise field that you want to set it lazy. You want only to read and instanciate it only when it is accessed.
If you done a getter at the start point, you can reimplement the getter in order to get your lazy function without any impact of the usage.

If needed, the direct access can be refactored to a getter in a proper interface with about 3 mouse clicks.
Until then, I just access directly.
(In my own personal little game projects, mind you. When working in teams on larger projects I don't work that way and stick to the generally accepted coding standards for obvious reasons.)

Sometimes I'd wish java would just let me define a field in an interface without needing to implement getters and setters that basically do nothing.

[actual]

Sometimes I'd wish java would just let me define a field in an interface without needing to implement getters and setters that basically do nothing.

Scala lets you do this.

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28

class Soldier {    var facingAngle:Float; } thisSolder.facingAngle = 300f; // Now let's say you want to clamp the value of facing angle between 0 and 360. class Soldier {   private var  _facingAngle:Float;     // EDIT - The  Getter that sproingie pointed out I was missing.   // (in scala, you do not need an explicit return statement. the function returns the last value.)   def facingAngle:Float = _facingAngle   def facingAngle_=(angle:Float) {       if (angle < 0) _facingAngle = 0       else if (angle > 360) _facingAngle = 360       else _facingAngle = angle    } } // Using it myNewSoldier.facingAngle = 400  // you can refer to it just like a plain old field println(myNewSoldier.facingAngle)    // prints 360

[sproingie]

You didn't define a getter that accesses _facingAngle, so wouldn't newSoldier.facingAngle actually return the default value of 0?

Having a language follow the Uniform Access Principle is still pretty keen though

Games published by our own members! Check 'em out!

[actual]

Thank you and getter is added.