java 变量的调用方法,Java方法调用与使用变量

Recently I got into a discussion with my Team lead about using temp variables vs calling getter methods. I was of the opinion for a long time that, if I know that I was going to have to call a simple getter method quite a number of times, I would put it into a temp variable and then use that variable instead. I thought that this would be a better both in terms of style and performance. However, my lead pointed out that in Java 4 and newer editions, this was not true somewhat. He is a believer of using a smaller variable space, so he told me that calling getter methods had a very negligible performance hit as opposed to using a temp variable, and hence using getters was better. However, I am not totally convinced by his argument. What do you guys think?

解决方案

Never code for performance, always code for readability. Let the compiler do the work.

They can improve the compiler/runtime to run good code faster and suddenly your "Fast" code is actually slowing the system down.

Java compiler & runtime optimizations seem to address more common/readable code first, so your "Optimized" code is more likely to be de-optimized at a later time than code that was just written cleanly.

tl;dr:

This answer is referring to Java code "Tricks" like the question referenced. It is not referring to correct design. For instance, I wrote a discovery routine to contact every computer in a class B network (64k addresses)--threading that was not an option and it was not an optimization, it was software design. Doing an insertion sort into an ArrayList is just bad programming, switching it to a LinkedList is not an optimization, it's a bug fix!