Re: Problem setting FontSize in CTreeCtrl

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 23 Feb 2009 15:53:19 -0800

Message-ID:

<#5U#8HhlJHA.5656@TK2MSFTNGP02.phx.gbl>

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:v816q4l777bilceof3kbldn3lb9j4qmjbn@4ax.com...

I find that most "programming conventions" that attempt to distinguish
global variables,
member variables, parameters, and local variables seem to relate to
programs created on
punched cards, and that use functions that are hundreds of lines in
length. A better
approach would be to not create programs whose complexity requires these
notations.

Note that Microsoft has a lot of _ variables that are used internally.
This opens the
possibilities for creating surprising conflicts.

But even simple programs benefit from using m_ for member data as opposed to
transient (stack allocated) variables. I'm using Qt now, and they don't use
any scope notation at all. I tried it their way but found it less
productive, not being able to instantly tell the scope of a variable. So I
went back to using m_, s_, g_, etc.

I suppose you're right that we shouldn't use leading _ as that conflicts,
but the alternative of a trailing _ is really bad. I haven't found anything
better than m_.

-- David