Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Bindevent to a property
Message
From
10/04/2013 16:54:47
 
 
To
10/04/2013 15:37:41
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01570434
Message ID:
01570677
Views:
62
>>The sad thing about Thor is that it also has the ability to validate whether or not there are any name collisions on a system when you know all of the tables in use, and have all the source code, yet such a report will not be created due to reasons specific to its developers' beliefs that the only proper solution is to prefix everything with "m." on variables.
>
>Rick --
>
>Please explain this statement. As far as I know, and I am the creator of Thor, there is no belief "that the only proper solution is to prefix everything with "m." on variables." In fact, I do not use use M.Dots (horrors!), nor have I ever encountered name conflicts as result thereof
>

Jim,

The fact that you yourselve have never ever encountered a name conflict although you donot respect the m.Dot prefix does not qualify the use of m.Dot to be something 'horrible' .

Fact is that by using m.Dot you will be guaranteed that your code cannot be broken or clashed when using as a procedure by an other programmer. It is a must, in my opinion, to make use of m.Dot in case you want to produce truly generic code. The disadvantage, in most of the opponents of using m.Dot is that it looks 'ugly'. Remember it is only coding and nobody can see the code, you are suppose to use it.
Luckely we have nowadays a procedure which can correct our codewriting to make it fully m.Dot compliant.
I remember one guy who was just like you, he was making all kinds of beautiful graphic applications for generic use, coding without m.Dot. The guy was facing a search and debug in his application for a whole day on a bug nobody else experienced, he could not reproduce. Than all of a sudden he realized the guy reporting the bug used a table with field(3) = N - of course you are correct this is a stupid thing to do - but my friends beautiful graphic application crashed on a line with if lcVariable = n and would not have crashed on if lcVariable = m.n
Please reconsider before you say again that m.Dots(horrors!)

Best regards,

Koen

P.S. better start a fresh/new topic about this matter as it seems we are a little bit away from the original subject
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform