Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Mdot question
Message
From
07/04/2021 02:49:37
 
 
To
07/04/2021 01:46:22
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Miscellaneous
Thread ID:
01679493
Message ID:
01679635
Views:
55
Likes (1)
I’m an idiot and I love tolerance to other’s opinion

>>>>>>SNIP
>>>>>>>
>>>>>>>>Why do that when it is not necessary, but ignore mdot when it certainly can be necessary?
>>>>>>>
>>>>>>>If you find yourself that it is necessary, it already is an indication there is something wrong. Column names should not conflict variable names in the first place. Granted, there are situations where this is out of your control, but in general your naming conventions should avoid this at all cost.
>>>>>>>
>>>>>>>To answer your question directly. For me it affects readability. As like Lutz, I hate it passionately.
>>>>>>
>>>>>>I don't care what you personally think or do. FoxPro works that way.
>>>>>
>>>>>That is a nonsensical answer. Coding practices have very little to do with how a product was designed. The latter is a human readable representation of instructions to the mechanics in the programming language.
>>>>>
>>>>>The fox isn't flawless. With the knowledge we have now it would not have been build in the same way as it is. There is a reason there is a good portion of commands and functions that are not commonly used anymore. The mdot would certainly not be part of VFP if it would not have to rely on its heritage.
>>>>>
>>>>>So I have no idea, what your implying when you say "FoxPro works that way".
>>>>
>>>>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.
>
>STRAWMAN
>
>FoxPro is build in such way you can ignore mdot entirely and build rock solid applications. Its not build in a way you are forced to use it.
>
>only an idiot can disagree with that.
Thierry Nivelet
FoxinCloud
Give your VFP application a second life, web-based, in YOUR cloud
http://foxincloud.com/
Never explain, never complain (Queen Elizabeth II)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform