This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
No laughing, please.... I have been taught that Hungarian Notation is the way the world does things. So why in Style Guide used for the Cattle Drive do they state: Hungarian Notation violates OO abstraction and is not to be used. Maybe the correct questions is, what is OO abstraction.
Don't worry, Michael, we're all laughing with you, not at you. You have been misinformed: Hungarian notation is not the way the (Java) world does things. Says Bruce Eckel in his book, Thinking in Java, p. 1052:
"Hungarian notation is the worst example of [creat[ing] your own "decorated" private data member names], where you attach extra characters that indicate data type, use, location, etc., as if you were writing assembly language and the compiler provided no extra assistance at all. These notations are confusing, difficult to read, and unpleasant to enforce and maintain. Let classes and packages do the name scoping for you."
So I think Mr. Eckel is trying to dissuade you from using Hungarian notation. It's a bad thing, don't do it! Art
I particularly like a section from the "ugly" from the above link:
Hungarian notation is, when all is said and done, a commenting technique. And the one great law of comments is that they lie. Comments are not syntax checked, there is nothing forcing them to be accurate. And so, as the code undergoes change during schedule crunches, the comments become less and less accurate.
Ahh documentation... OP
Joined: Sep 29, 2000
Of course you are making an exception for MY documentation - yes???