Re: [android-developers] Re: Singletons in Android .... Final solution?
Please follow the Java naming conventions.
There is nothing wrong with his naming conventions...
No prefix "m" is necessary, although for some reason many
people do that, and underscores are not conventional.
You are correct, the prefix is not necessary, but it is often used as a way to distinguish between member variables of a class (hence the 'm') and local variables. In my opinion it makes things easier to understand when reading code... You immediately know if the variable is going to change the state of your class or not. There is also nothing wrong with using an _ in the variable name. Just because his naming convention is not the same as yours doesn't make it wrong.
Use camel case, as 'mInstance' (if you must use the wart), or just 'instance'.
He is using camel case, with the sole exception of the "m_" prefix.
mThisIsMyVariable or m_thisIsMyVariable... what does it matter? You don't need to criticize something as trivial as this.
mThisIsMyVariable or m_thisIsMyVariable... what does it matter? You don't need to criticize something as trivial as this.
Thanks,
Justin Anderson
MagouyaWare Developer
http://sites.google.com/site/magouyaware
On Fri, May 4, 2012 at 3:03 PM, Lew <lewbloch@gmail.com> wrote:
Please follow the Java naming conventions.No prefix "m" is necessary, although for some reason manypeople do that, and underscores are not conventional. Usecamel case, as 'mInstance' (if you must use the wart), or just'instance'.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home