News for hackers. Stuff that matters.
Re:Google's updated Java coding guidelines by guelo on Wednesday January 29, 2014 @08:49PM (#7148569)
I'm glad they got rid of the stupid m for mFieldName, it's been infecting all the Android developers.
Re:Google's updated Java coding guidelines by myko on Wednesday January 29, 2014 @09:05PM (#7148644)
This 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
Re:Google's updated Java coding guidelines by yla92 on Wednesday January 29, 2014 @10:18PM (#7148865)
It'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-fiel...
Re:Google's updated Java coding guidelines by danielkutik on Wednesday January 29, 2014 @10:51PM (#7148979)
I 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.