You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your guidelines you're using Hungarian notation (adding a prefix to variables to indicate their type).
This is a practice that has long been rendered obsolete and counter productive.
Why should you have a cDescription or iNumberOfOrders instead of description or numberOfOrders?
What could description possibly be other than a string? And why should you care?
A good name for a variable is enough to know what you're dealing with, if you need to know this at all...
The text was updated successfully, but these errors were encountered:
Like @LievenDeFoor said, it's Hungarian notation. Idea here is actually prefix type and in few cases kind (global vs parameter vs local) of variable to make code more readable. Not everybody moved to OE Development Studio (it helps there too), some people still use Progress Editor, some people make changes using mpro and it actually helps a lot to see what type/kind of variable you work with without scrolling back and forth. In most cases good variable name is all you need, but when you work with large teams it helps to keep code cleaner (and code review simpler) as everybody know how to prefix variable, not everybody can come up with good, short and meaningful variable name (as example lastModifiedDate is it DATE, DATETIME or DATETIME-TZ or formatted string?).
In your guidelines you're using Hungarian notation (adding a prefix to variables to indicate their type).
This is a practice that has long been rendered obsolete and counter productive.
Why should you have a cDescription or iNumberOfOrders instead of description or numberOfOrders?
What could description possibly be other than a string? And why should you care?
A good name for a variable is enough to know what you're dealing with, if you need to know this at all...
The text was updated successfully, but these errors were encountered: