>Mike,
>
>>That is two standards - the percentage is irrelevant. Just as "faster" is "faster" no matter the percentage.
>
>Code readability is far more important in the long run of an application than shaving microsecond off loop execution speed.

Honestly the m. doesn't interfere with readability in the least.


>
>And more seriously if developers are writing loops that have thousands or more iterations in an interpretted language like VFP they need to evaluate higher performance options. I've seen far too many examples where a single SELECT or UPDATE SQL statement could have been used rather than a loop. Too many FoxPro developers are stuck back in 2.x mentality.

I've done SQL commands against million plus record tables where the use of m. made noticeable differences.