Re: Tool for inlining useless getter/setter call
Jack wrote:
Daniele Futtorovic a 9crit :
On 2008-02-12 10:45 +0100, Jack allegedly wrote:
Daniele Futtorovic a 9crit :
On 2008-02-12 08:53 +0100, Jack allegedly wrote:
Owen Jacobson a 9crit :
On Feb 11, 9:25 am, Jack <mls...@poqsd.com> wrote:
Hi,
is there a tool to inline "useless" getter call:
* simple getter (return field;) or setter (this.field = arg)
* called in the class that contain the field
* getter/setter is not overloaded, and does not overlead (in the
current code)
I would like to inline these call automatically in all my java code.
Sun's Hotspot JVM (and presumably any other JITing JVM) is capable of
inlining these at runtime and will do so automatically unless JIT is
explicitly disabled.
Thanks, but i would like to remove them from the java source code.
The reason is that these accessors hide "what is going on", and i
don't appreciate that.
This sounds like the very contrary of what you should strive for (see
the UAP link Daniel Pitts posted).
Could you elaborate on your reasoning?
Daniele:
it's the least of our problems. My boss don't care about anything
execpt testing for null everywhere. I didn't even know the word
"JavaBean" before i was hired.
So i really don't care about concepts like "UAP".
This is not so much about Beans as about encapsulation. Instance
property access through methods is arguably an important aspect of good
coding, for polymorphism, maintainability and adaptability.
I would say whether or not you concern yourself with the quality of what
you produce is a matter of self-respect. Your boss' opinion
notwithstanding.
The thing is, HE define the specs, HE change them every week, so i just
can't make a good model/design and then implement it.
Now half the time i have to work with code produced by him, so i don't
want to develop two "personality" for two kind of code. Every time i
must find a bug in his code, i can't think "this shouldn't be done like
that". So i'm just resigned.
First, take a Java coures and OO design course.
Second, get a job with a manager that doesn't micro-manage.
The whole idea of OO is to "hide" unnecessary implementation details,
your "goal" seems to be to expose those details. Its almost like going
to a restaurant and insisting on watching how they kill the cow for the
steak you're about to eat.
Also, Java automatically "checks for null" for you. That's what the
NullPointerException is for :-)
--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>