On 26.06.20 16:04, OCsite wrote:
Hi there,
note please that IMO, /this.foo/ definitely should go through the
/getFoo/ getter if there's one; that is does not happen currently I
regard as a pretty grave bug, for it breaks encapsulation. Compare
please e.g.
the counter example is always:
public class X {
private String foo;
public String getFoo(){ return this.foo; }
public void setFoo(String foo){ this.foo = foo; }
}
This works perfectly fine in Java and would lead to a stack overflow in
Groovy as soon as you call the getter or setter. Since it is quite
common we have a problem here.
bye Jochen
