E>public boolean getCurrentEdge( Edge edges[] ) throws Exception
E>  {
E>    Edge current = new Edge();
E>    edges[ 0 ] = current;
E>    ...
E>    current.setLength( calculatedLength );
E>    ...
E>    current.setWidth( calculatedWidth );
E>    ...
E>    return result;
E>  }
E>...
E>Edge current[] = new Edge[1];
E>getCurrentEdge( current );
E>...
E>

LCR>class EdgeBean
LCR>{
LCR>    private Edge edge;
LCR>    public void setEdge(Edge edge) { this.edge = edge; }
LCR>    public Edge getEdge()          { return this.edge; }
LCR>}

LCR>public boolean getCurrentEdge(EdgeBean bean)
LCR>{
LCR>    bean.setEdge(new Edge());
LCR>    return true;
LCR>}
LCR>

E>Properties are just syntactic saccharine for getter and setter member functions for individual fields.
E>C++ experts have spent years trying to educate people NOT to use public data, to use member
E>functions instead, and now we propose to introduce something that looks just like public data? Do
E>we really want to try to teach people that public fields are still bad, but properties are good, even
E>though they look just the same from outside the class? Moreover, these public fields have side
E>effects!