>>>However this discussion is more about the hungarian notation, where the prefix is indicating type and scope. Since 99% of all variables are (should be) local there is no need to indicate scope unless it is a public or private.
>>
>>FWIW, I agree with you on the scope issue. I use a scope prefix only for the rare public variable, but I find the one letter type indicator extremely valuable.
>
>I find the scope prefix to be helpful. For example, you don't have to scroll up to the LPARAMETERS statement to determine whether a variable was passed as a parameter or declared as LOCAL in a routine.

On this one I love the t (for parameTer) prefix. Most of the time (and I'm getting less and less lazy on that one), my parameters are called tcSomeString, tuValue ("u" for "undefined or pretty much any type"), ttTime etc.