The way I understand it, it is more like lnLoopCnt, tnPara, laDropList, etc.
At least that's what I've been trying to be disciplined to do because it helps ME maintain and support my own code. It's often a case of helping me remember what I was trying to do years down the road. I'm a firm believer in finding a style that works for you and then sticking to it in everything you write. Maybe that is outdated, but that's just me.
I also try not to duplicate like "ldDueDate", or "lnInvNum".
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Wednesday, July 26, 2017 1:56 PM To: profoxtech@leafe.com Subject: Re: Variable/Procedure Naming Conventions
On 2017-07-26 13:37, Paul H. Tarver wrote:
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.
What is the YAG naming convention? lcName, ldDue, or is it more CamelCase like DateDue?
[excessive quoting removed by server]