Hi del,

>You guys are missing the point. It's not a matter of work ethic or know how. Rather, it takes time to look things up. Time is a scarce resource. Small bits add up over the course of a project. Further, it becomes more important when you are working on something with complicated logic and you are trying to keep straight the variables you are using. Yet another example - I don't use private vars very often, but when I do the scope designator is beneficial because the variable may not be declared in the routine I'm currently editing.

I think you guys miss the point. Naming conventions are *not* helping us to read the code. I've never felt that naming convention helped me in any way. Whether or not using naming conventions, I still should know when, why and what a variable could/should contain. You can't tell this story with naming conventions. In good coding practises, naming conventions (aside from giving a variable a descriptive name) are at the far bottom of the list making your programs clear. It is about irrelevant.

Walter,