>>
>>Thanks, but I'm well aware of the issues.
>>
>>Readability, "searching", and any reduction in (my) coding errors due to field/variable name conflicts are more important (to me) than any tiny increase in performance.
>
>
>For the sake of those lurking:
>
>- 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.

>- 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.

>- 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.

IMO it's all a metter of personal preferences.