Avoid Internal Getters/Setters
Avoid Internal Getters/Setters
In native languages like C++ it's common practice to use getters (e.g.
i = getCount()
) instead of accessing the field directly (i = mCount
). This is an excellent habit for C++, because the compiler can usually inline the access, and if you need to restrict or debug field access you can add the code at any time.
On Android, this is a bad idea. Virtual method calls are expensive, much more so than instance field lookups. It's reasonable to follow common object-oriented programming practices and have getters and setters in the public interface, but within a class you should always access fields directly.
Comments
Post a Comment
Please post comments here:-)