RE: Subprocedure invocation (was on RPG List)

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

OK, this is moving into Java/.Net land, so to keep David happy, I'm
moving it to the Java list... :)

> Ah yes, opinion.  <grin>  Try telling the folks in the SWT development
team
> about accessing member variables.

Member variables vs. property getter/setter is somewhat opinion, yes.
But since I don't know SWT (and I'm not going to learn it :) why did
they do that? A property getter/setter provides you a _possibility_ of
changing/enhancing the get/set process at a later date, where direct
variable access locks you out of that. The only reason I can think of
for direct access is one of performance, but I'd think that any decent
JIT compiler would optimize out the trivial getters/setters anyway.

> I'll tell you why I like Java's technique...

Fair enough. And it is a style difference. The reason* I prefer the
opposite is that is it provides me a option down the line I don't
otherwise have. And actually all our business object property
getters/setters do more than a simple variable read/write anyway, so we
need that functionality. 

> Brand New 2008 Joe Pluta...

Complete w/leather and that new car smell???? :)