Timeline for Why did Microsoft make parameters, local variables and private fields have the same name naming convention?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 6, 2011 at 23:31 | comment | added | Jason S | To elaborate a bit on this, I always prefer this, because it definitely refers to the current instance whatever house you're at, so it is precise. The underscore or underscore m conventions are just that - conventions that may or may not refer to instance variables and they are made redundant by this. The only place I see underscore useful is in case-insensitive VB to distinguish object and class names. But that is a whole other story. | |
| Aug 15, 2011 at 19:01 | history | edited | Adam Lear♦ | CC BY-SA 3.0 | added 233 characters in body |
| Aug 15, 2011 at 18:53 | history | answered | Adam Lear♦ | CC BY-SA 3.0 |