>>It is strange that we can easily find such "no-mdot practice" in the xBase code of many VFP built-in tools. Can anybody explain the rationale behind it?
>
>It's not a rationale. It's a preference not to use it. At worst it's ignorance of the dangers.
>


"Ignorance" is a strong word.

Although missing "m." in code of tools is obviously an issue for public users, there are still quite a few VFP experts, including those who wrote code for the built-in VFP tools, sticking to the practice. There must be either some reasoning or historical factors for the practice.

Ben