The convention for using m_ prefix is used to signal visually what is a private member and also p_ prefix is for params. I don't like it that much and I've seen it both in Java and .Net but, if I'm working on a code base which uses this convention I;ll simply stick to it. Consistency is nice, inconsistency not so.
Well, this.field also can be used to signal visually what is a private member or what is a private method. And it's supported by the language, and there's no need to use such magic prefix strings.
My point was that the same people who insist that 'this' is superfluous because "IDE can handle it" are also advocating use of "m_" because of "visual signal". I simply think 'this' is superior to "m_" in every way.
