|During the last couple of years, I have worked on various code bases, some of which used Hongarian notation, some of which used a bastardised attempt at Hongarian, and some which had pure CamelCasing.
I must say, that with time, one stops caring, as long as the code is solid and logic well documented. However, I must admit, that if I have a choice, I will always employ a subset of Hongarian, and prefix member variables with a m_, ints with a n etc...
However, I have also bastardised Hongarian notation to suit my purposes, with a variation where class names are acronym-ised and prefixed to variable names (not pointers), such as:
// then again, I do have Intellisense, so typing these things is not a problem for me
On the subject of pointer variables, I always prefix with a p and then follow with a description of the object...
Anyway, the point I'm trying to make is that notation is important, but is also localised to the team or teams that will work with the code. If you work on an OSS project, I feel it would be good to have a standard notation that all contributors adhere to...
Just my 2 South African cents
[WinShareSpy] [Glossary Manager] [AfterThought Backup Lite]
All good things were meant to be improved