RE: Getters/Setters vs. member access (was: Subprocedure invocation)

From: Walden H. Leverich

It's funny, I think the difference is one of grouping too. With the java
approach you're thinking in a ActionObject approach, where the .net
approach thinks in the ObjectAction approach (where action in inferred
from usage).

Eh, I guess I can see that, although really:

myobj.myvar = x;

myobj.setMyVar(x);

Is the grouping really that different? In either case the object is myobj,
and you're executing an action on that object (setting myvar). You could
probably even argue that the Java approach is more strictly OO, because
you're sending the "setMyvar" message to the myobj object. There is no
message/receiver relationship in the .NET syntax, and in fact it looks as
though the property itself is the receiver, which isn't true - it really is
the object receiving and acting upon the message.

But now we're truly drifting off into the chasms of ultra-nerddom. In fact,
I have a sudden urge to break my glasses and tape them...

Joe