I myself am not fond of prefixes, especially since languages like Java
already have this. when you need to distinguish local vars vs
members. Also, modern IDEs highlight fields differently from local
variables.
It does make sense however on a project like Android where not
everybody is
Hi guys,
I saw many sample codes that each variable contains the 'm' prefix. I
don't know what this m means.
I have two-year experience in MFC. Each variable has 'm' prefix to
tell you that I'm the one variable of MFC component. (m stands for
MFC).
So...can anybody answer me this question?
It stands for member. I believe the use of an m prefix with MFC
has nothing to do with the name MFC either, but rather to identify
variables that are class members as opposed to local variables for
instance.
On Sun, Feb 21, 2010 at 9:52 PM, Christ wutie...@gmail.com wrote:
Hi guys,
I saw many
I'm one of those guys who think scope prefixes, like m, are more trouble
than they're worth. The fact that you had to explain it to a newbie makes me
smile.
On Sun, Feb 21, 2010 at 10:04 PM, Romain Guy romain...@android.com wrote:
It stands for member. I believe the use of an m prefix with MFC
On Sun, Feb 21, 2010 at 10:20 PM, Frank Weiss fewe...@gmail.com wrote:
I'm one of those guys who think scope prefixes, like m, are more trouble
than they're worth. The fact that you had to explain it to a newbie makes me
smile.
Well you probably need to explain many other things to a newbie
On 2/22/10 2:20 PM, Frank Weiss wrote:
I'm one of those guys who think scope prefixes, like m, are more
trouble than they're worth. The fact that you had to explain it to a
newbie makes me smile.
I use m_ purely so I don't have to think up different names for my
method parameters and to
6 matches
Mail list logo
