Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The m. variable thing, the sequel
Message
From
21/12/2004 09:02:22
 
 
To
21/12/2004 08:32:06
Mike Yearwood
Toronto, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00969478
Message ID:
00970951
Views:
76
>>Mike,
>>
>>>>Again, IMO, you're fighting an acedemical issue that has little value/application in real life in most cases.
>>
>>>If you don't feel it is significant, then why do you constantly involve yourself in mdot discussions where you argue against mdot? Especially when your argument is completely based on your personal preference without any technical reason against using mdot?
>>
>>Everyone has the freedom to respond on things that in their opinion should not be pushed down our throats. I took this liberty, because I find that there is more to say about it. And again it is not only based on MY personal preference, but also based on the personal preference of other well known and respected VFP developers.
>
>No one is pushing anything down your throat. The fact is only dbase-like languages have this issue. How you deal with it is your affair. I know several really good VFP developers and they're using mdot. IMO technical reason must outweigh personal preference.
>
>To use analogy, most programming languages are like pants with buttons in the front. VFP is like pants with a zipper. There is a chance that something might get caught in the zipper. I think wearing underwear will reduce that risk. You can certainly arrange things so nothing gets caught in the zipper. Also, in the case where the temperature gets down to -30C, you will be less ... protected. You'll still have risk. You won't be able to zip up quickly and without care. You don't want to wear underwear because they make pantylines on your ahem ... backend - you don't like how they look.
>
>I think it's just easier to put on the underwear! I'm talking safety, you're talking fashion. ;)
>
>How's that? ;)

Hi Mike, I do not want to speak for Walter, but i think that he has understood all the differences.

You speak about safety,
but is more probable to have one field-variable collision with the Walter's protocol (totally different syntax names)
or with equal names (SCATTER TO MEMVAR) and always using the prefixed one mDot?

Enough to make a small calculation and one looks at that the method of Walter is surer;
of course he does not have to never use MEMVAR.

I make a speech of formal correctness, not of safety.
If we want the safety, the VFPT must add a SET that it obligates to put mDot for get a variable's value.

Fabio
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform