>>>>>>>Hi.
>>>>>>>
>>>>>>>does it make any sense to have mdot used like this
>>>>>>>

>>>>>>>m.ObjName1.Name2()
>>>>>>>

>>>>>>>?
>>>>>>
>>>>>>The final point in this is again, that is how FoxPro works. If you want to ignore it, that's stupid.
>>>>>>
>>>>>>I have code where the original programmers did
>>>>>>
>>>>>>SCATTER NAME aliasname.
>>>>>>
>>>>>>Now, not only is mdot for fields an issue, but also m.aliasname to differenciate the cursor from the object name. It wasn't until the object name feature was added. These guys did not ever come to the user group meetings, or any online forums. They thought they knew better and here we are.
>>>>>
>>>>>Do you repeat your messages, or is LevelExtrem broken? I've answered this before.
>>>>>
>>>>>You run in circles with this non-argument that is how FoxPro works It is simply not true. It works without pretty well. Crappy XBase code is not the standard. I have less then 10 methods that touch GATHER SCATTER or something the like. Those are the only points where alias or field could cross a variables name. This should be used carefull, but for 99.9999% it's meaningless.
>>>>
>>>>Why are you *not* understanding what he means by that phrase "that is how FoxPro works"?
>>>>
>>>>If I'm not mistaken, it is being meant to convey that FoxPro has certain "quirks" in behavior (e.g. prioritizing field names over variables) and that use of mdot can be used to work around some of the problems (amongst others) that this behavior can cause. As you indicated you can avoid these problems by proper design, but if you're having to deal with existing code (that someone else wrote) you may not have that option to redesign it (nor do you want to even try -- there's a good chance you'll break something if you do) -- so you basically try your best to work within those confines.
>>>
>>>I read this different. The way and order how VFP tries to find a meaning for a name is clear as blue sky and where never doubt by me. I only say that this stubborn I know how it goes and this means vars only with mdot and mdot everywhere is wrong. And mdot on left side of an assignement or on an ARRAY access is nonsense.
>>>
>>>That crappy old cold need delicious handling is one thing. But spread this over any code is wrongness.
>>
>>That is only your opinion.
>
>As you have guessed by now, not only LUTZ's opinion.
>
>> It is not backed up by the fact that FoxPro STILL looks first for a field named like your variable reference and still looks for an alias like your object reference.
>
>That is irrelevant when you code in a way you should be coding in the first place: Making sure your variables do not share the same naming conventions with fieldnames.
>
>>You wish to let it waste time doing so because you don't like how some code looks. That is shallow.
>
>I'm obviously much more concerned with the readability of code than you are. Over the lifetime of any respectable lengthy project, the readability of source code is the one of the most important issues. If its not readable, it is not maintainable and will cost tremendous amount of time when you have to revisit the code again. I had to learn that the hard way.

Again insulting. I know exactly what is readable. I am often dealing with code from idiots. The did not use any naming convention, they did not use built in FoxPro features and rolled their own buffering. I code so my code won't break no matter who gets it. Unlike you.