I was reading a chapter on 'Meaningful Names' in the book "Clean Code" by Robert C. Martin last night and right after he made a big point of using "Intention-Revealing Names" ie: make the name of a variable, procedure or function reflect its use, he then takes the opportunity to trash the Hungarian Notation system (and by extension I suppose any similar naming convention, including the YAlan Griver convention) saying that with today's strongly typed variables, notation like this is useless and should be avoided.
Quite frankly, it hacked me off as I've spent the better part of 25 years learning and becoming disciplined enough to use the YAG naming convention as well as I could in FoxPro and I've used the same naming convention regardless of the language or its strongly typed variables because it works for me. In my world, any roadmap or breadcrumbs I can leave myself for future maintenance and standardization is a good thing. Thoughts? Paul H. Tarver Tarver Program Consultants, Inc. Email: <mailto:[email protected]> [email protected] --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
