Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upHungarian Notation #4
Closed
Comments
|
Kotlin has no fields (only backing fields) but Properties. The m-Prefix doesn't make sense here. In worst case it would create getters such as Don't use the m-Prefix in Kotlin |
ASOP Java Code Style is for Android Open Source contributors, and should not be followed unless you're contributing to Android Open Source Project. I think it's better if the style follows the naming section of Google Java Style |
Rainer-Lang
added a commit
to Rainer-Lang/AndroidCodeStyle
that referenced
this issue
Oct 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the AOSP Java Code Style for Contributors:
Our developer survey shows that we overall like the "identifier metadata" and will stick to this convention.

We don't believe that "Today, our IDE’s can distinguish all these identifiers with colors so we don’t need any of this any more" because we often read code outside of IDEs when reviewing code.
Cédric Beust outlined his decision to introduce the
m-prefix in his article "I am the reason for Hungarian notation in Android". Read this for further arguments for them-prefix.