>Yes, that can happen and that is one of those special cases I am talking about. Also, if somebody has LCFILENAME he might as well have LCFILENAME variable somewhere. In this case non-generic and very specific variable names help avoid such situations. In case of public domain classes you might use non-standard prefixes to variables to avoid this.
>But if you are working on your application with your chosen framework which you know everything about such situation should not happen if you follow the naming convention.

Quite recently I made a reverse mistake. I named field in a table lTownName (or something like that). I was reading my program and changing variables to preceed with m. according to my new style. I came to work on Friday and found a harsh letter from my manager, that one of my program failed and it took him a considerable amount of time to trace this problem down. Well, all I could tell him: don't touch my programs and let me fix my problems by myself :)

Another situation was with my colleague. She usually doesn't declare variables and uses some weird names like foo or SaveAli. One of the program was doing something strange. Finally we found out (after ~1h. investigation) that she used this SaveAli in two processes, therefore the top program restored incorrect alias...