>Okay - could you share an example of "usual" VFP coding techniques campared to "Hungarian" VFP notation? Whatzit look like?
The notation recommended by MS would use something like:
lnAge
where "l" stands for "local", "n" for the type, "numeric", and then comes a description of the content.
Similarly, for objects (placed on forms, for instance), you would start with three letters, like Txt for TextBoxes.
As I understand the article, it would be better to define your own "types", depending on how the variable will be used.
For example, applying this to VFP, if you have a TextBox, derived from a class to handle monetary amounts (currency type; appropriate InputMask), instead of calling it TxtPurchasePrice, you might name it MoneyPurchasePrice, for example. The same (I think) if you create the TextBoxes directly, without using classes. This would give you much more useful information than the mere fact that it is a TextBox.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
