Thanks Megha.

On Mar 27, 4:42 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> There are no published guidelines for Android coding conventions.
> A few guidelines are given in this 
> document:http://code.google.com/android/toolbox/performance.html
>
> These are largely same as the coding conventions for Java, except for
> prefixing variable names with 'm', and using four space indents(it falls
> within standard 2 to 8 spaces range) and perhaps a few other
> exceptions..However, if you follow the NotePad tutorial closely, it is a
> good example of Android coding conventions.
>
> Thanks,
> Megha
>
> On Wed, Mar 26, 2008 at 1:41 PM, Rui Martins <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > Some people use "m" as prefix for all class fields. "m" stands for
> > "member" variable or field.
>
> > I don't like this specific convention, and I don't use it, and if I'm
> > not mistaken, this is not a java recomended convention.
>
> > If we really need to make obvious in some specific situation, that
> > something is a member variable, I use:
> >   this.variableName
>
> > But if this need arises often, there must be something wrong with the
> > application class architecture, in my opinion.
>
> > See ya
> >    Rui Martins
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to