Databases
StackOverflow2013
Postsdbo
POAndroid private fields naming guidelines are ok?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid private fields naming guidelines are ok?
    primarykey
    data
    text
    <p>Here <a href="http://source.android.com/source/code-style.html#follow-field-naming-conventions" rel="nofollow noreferrer">http://source.android.com/source/code-style.html#follow-field-naming-conventions</a> it is stated that :</p> <blockquote> <p>Field Names</p> <ul> <li>Non-public, non-static field names start with m. </li> <li>Static field names start with s. </li> <li>Other fields start with a lower case letter. </li> <li>Public static final fields (constants) are ALL_CAPS_WITH_UNDERSCORES.</li> </ul> </blockquote> <p>It also states that :</p> <blockquote> <p>The rules below are not guidelines or recommendations, but strict rules. You may not disregard the rules we list below except as approved on a need-to-use basis.</p> </blockquote> <p>I don't like the "m" convention before private or package fields in a class. I really find this uninspired... I mean, if we try to apply good designs, the low coupling of the classes implies having few public fields. actually, in my programs I usually have no public fields, even when I need some I use getters and setters... </p> <p>So, why should I be forced to have almost all my fields in the program with an "m" in front of them? wouldn't be easier to have the few public fields, if there are any, with some "g" in front or something? or just use setters and getters as beans suggest? this really makes my code harder to read.... </p> <p>Also, following these guidelines, local temp variables used in the methods have no restriction so they could easily be mistaken for public global fields (also without restriction)... this also I find to be wrong, as it is a probable source of mistakes... I understand to have a way of differentiating from fields, but private/protected member fields are the most used in an application, they shouldn't be less "readable".</p> <p>What do you think? Should I follow the guidelines?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGabrielOshiro
    1. USCristi Ba
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. This table or related slice is empty.
      1. VTDownMod
    1. COOne of the reasons prefixes like this are often mandated is to prevent hiding the member fields. For example you often have a parameter to a constructor or setter method that is the same name as the member field if you don't have any prefixes. In such cases you then have to access the member field using "this." in front of it whenever it is hidden. Programmers occasionally forget the "this.", which leads to bugs. A prefix on public fields isn't as useful because there is no need for a setter on a public field anyway.
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. USLance Nanek
    2. COi actually prefer the m_ prefix on private fields because it makes your class methods easier to read. These conventions are used because code is read more than its written... I think thats in Code Complete somwhere?...
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. USDavid Rogers
    3. COi agree with you.. i dont like the "m" convention and i am happily not using it
      singulars
      1. POAndroid private fields naming guidelines are ok?
      1. UShendrix
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload