Considering that most people that use Hungarian Notation is following the misunderstood version of it, I’d say it’s pretty pointless. If you want to use the original definition of it, it might make more sense, but other than that it is mostly syntactic sugar. If you read the Wikipedia article on the subject, you’ll find … Read more
Are variable prefixes ( Hungarian ) really necessary anymore? NO! In fact, Microsoft’s own style guidelines (where the practice originated) now recommend against it. In particular, see the section on General Naming Conventions, which includes the following text (in bold type, no less): Do not use Hungarian notation. Of course, these guidelines are not binding … Read more
The k means constant in hungarian notation… see Lower case “k” in Cocoa.
I like the underbar prefix for member fields. Mostly I like it because that way, all of my member fields are shown alphabetically before my methods in the wizard bar at the top of the screen.
It’s a historical oddity, still common practice among teams who like to blindly apply coding standards that they don’t understand. Long ago, most commercial programming languages were weakly typed; automatic type checking, which we take for granted now, was still mostly an academic topic. This meant that is was easy to write code with category … Read more
vUsing adjHungarian nnotation vmakes nreading ncode adjdifficult.
This is typical programming practice for defining variables that are member variables. So when you’re using them later, you don’t need to see where they’re defined to know their scope. This is also great if you already know the scope and you’re using something like intelliSense, you can start with m_ and a list of … Read more