Re: the Java Lang will support Properties in Futuere?

mttc wrote:

the answer is simple. it's true! the get and set it's good. The
problem is when we use it:

i=s.getX();
s.setX(i);

I see no problem with this.



why Java (after so many years) not able to give us simple code (as
Delphi):

i=s.X;
s.X=i;

I don't like Delphi.



There have many debate and page on the Internet. I say to java Leaders
do what developer ask!

Yes, do what developers ask, don't change it. Leave the setters and getter alone.


And why the Netbean not support get & set when the list of members
pop, why we got the getXX separate then setXX for the Same properties?

Because there are read-only (just getX) and write-only (just setX) properties?


Sorry but I don't see any call for emulating Delphi. I'm afraid you are a voice crying in the wilderness alone.

.

Relevant Pages

  • Re: News for Java?
    ... The "accessors of evil", as I think someone once said. ... sparing and conservative when it comes to providing setters - which I ... Bean developer providing an unnecessary setter. ... were caused by a setter putting an object into a logically inconsistent ...
    (comp.lang.java.programmer)
  • Re: the Java Lang will support Properties in Futuere?
    ... do what developer ask! ... getter alone. ... my understanding is that it is heavily discussed for Java 1.7. ...
    (comp.lang.java.programmer)