No, agreed, and is my one reservation on continuing to use m_ in the Java world since there is such a huge body of code that has decided not to. (this was less

No, agreed, and is my one reservation on continuing to use m_ in the Java world since there is such a huge body of code that has decided not to. (this was less of an issue 15 years ago when I started) If I'm working on an existing body of work I take on whatever convention is used of course. As for mixed in a file, there's just no excuse for that. If you are the kind of religious zealot that thinks her rightness in bracketing style or naming convention is so superior that it should override the convention used in a file then you have no business coding on a team.