>>>- In this case, fields and variables can't be confused because you can't use fields on the left side of an assignment =.
>>
>>Readability decrases because the same name could be a variable or a field depending on wich site of assigment it is.
>
>Actually, no...you can't use a field on the left side. It will always be a variable or property.

Actually yes, because it's not the case for the right side of assigment.

>
>>
>>>- Readability gets more difficult (IMO) because there are more characters for the brain to interpret
>>
>>Reability increases because m. prefix tells the brain right away that its a variable not a field and vise versa.
>
>See above

Looks like you ran out of arguments here

>
>>
>>>- The "tiny increase" could get very large inside a loop. I've timed the differences to be three times slower.
>>
>>I just run a test: 1,000,000 itterations on AMD 1.3Ghz: With m. .590 sec, w/o .571. The difference is realle negligible.
>
>How did you conduct your tests? If not set up properly, you will get your results.

I ran two simple FOR loops with 1,000,000 itterations incrementing variable lnCounter inside. One with m.lnCounter on the left side of assugment, another with lnCounter

m.lnCounter = 0
m.Start = SECONDS()
FOR i=1 TO 1000000
    m.lnCounter = m.lnCounter + 1
ENDFOR
? SECONDS() - m.Start

m.lnCounter = 0
m.Start = SECONDS()
FOR i=1 TO 1000000
    lnCounter = m.lnCounter + 1
ENDFOR
? SECONDS() - m.Start

>
>>
>>IMO it's all a metter of personal preferences.
>
>I believe I said that.

At least we can agree on that :)