Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The m. variable thing, the sequel
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00969478
Message ID:
00974694
Views:
61
George;

Every place I have worked as a programmer I have introduced coding standards. I like to work in an environment with code that others as well as myself can read. It makes a programmer’s job easier.

Having said that I made a good deal of money and was able to support my family for several years by being called in by different companies to fix problems with FoxPro/VFP code left by others. I am very good at such things. Too many programmers write code that is difficult to understand, not commented, and not efficient. I love puzzles and this is fun to me.

My motto is, “Fix the code and do not worry about inefficient code written by others. Leave inefficient code alone unless you are paid to do otherwise”!

If everyone writes well-commented code that follows standards, and works, a good source of employment will disappear! :)

Tom


>>Mike,
>>
>>>It is simply obvious that if you have some rules in place that limit your exposure to mdot issues, that you are 1) less experienced with dealing with them and 2) limiting your environment.
>>
>>I don't quite understand what experience has to do with. FYI, I did use mdot in the FP2.x days but went away from it. I know all the circumstances where to use and not to use mdot. I know all known technical details surrounding the mdot. Further I know that there are lots of less experienced or less professional people fall into the trap of not using mdot when they should. How does this make me any less experienced than anybody using mdot ??
>>
>>My point is: Personally I don't see any reasons to use mdot in my projects unless there is absolute need to, because:
>>
>>- Collisions of fieldnames and variables are avoided.
>>- It is my personal preference not too use it.
>>
>>And that is the bottom line. You can agree with it or not, but that is the way I've been doing it since I started using VFP.
>
>Walter,
>
>The only place I use the mdot convention is in the command window because Intellisense kicks in.
>
>The only reason for naming conventions is to make the code more readable.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform