>>>>>>He's saying that FoxPro has a way it disambiguates names and you can work with it (use mdot where it's called for) or you can do it the hard way by having a whole set of rules to try to avoid conflict rather than adapting to reading code with mdot in it.
>>>>>
>>>>>Foxpro offers a mechanism of explicitely differentiate between variable and fields. But that is a far cry from the claim that "FoxPro works this way", as proven by the fact you can perfectly write rock solid programs without it.
>>>>
>>>>FoxPro is built that way. Only an idiot can disagree with that. It looks at a field before a memvar. It looks at an alias before an object. That is how it is built. Stupid to hear from the stupid who don't understand simple facts.
>>>>
>>>
>>>Mike, I agree with you on using mdots wherever ambiguity is possible. But you do nothing to advance the argument by calling people idiots or telling them they are stupid. That behavior is uncalled for.
>>
>>Too bad. Many people had berated me over the years in worse ways with no help from this "community".
>
>Mike - I've learned a lot from over the years (even in cases where we disagree). I don't want to put you on my mental list of people I ignore because it's worth wading through the nastiness. Please reconsider.
>
>You can characterize an idea as stupid without characterize the person expressing it that way (though I think there are better ways to change minds).
>
>And FWIW, I've called out others in VFP forums for going too far.
>
>Tamar

Those who cannot be convinced by logic and reason, and choose to make a decision based on cosmetics are stupid. I often inherit code from others and using mdot has never once caused my additions to crash, and has often fixed the crashes of these "geniuses".