3 ms·
I'm glad they got rid of the stupid m for mFieldName, it's been infecting all the Android developers.
by guelo 13y ago
I'm glad they got rid of the stupid m for mFieldName, it's been infecting all the Android developers.
- myko 13y agoThis has never been part of Google's internal guidelines. This is part of the Android guidelines which are separate and available here: http://source.android.com/source/code-style.html http://source.android.com/source/code-style.html
- yla92 13y agoIt's just because it's stated inside the Android Code Style Guidelines for Contributors. I see a lot of other people, especially Android developers, use that field name conventions too. There is not only mFieldName, there are sFieldName for static variable as well. http://source.android.com/source/code-style.html#follow-field-naming-conventions http://source.android.com/source/code-style.html#follow-fiel...
- danielkutik 13y agoI really hope they work on the Code Style Guidelines for Contributors. But even the generated source code (like resources in R.java) should adhere to these guidelines.