underscore prefix

[mike parr]

A few times when looking at code on the net I have seen objects,
variables etc prefixed by an underscore. But I've never seen any
explanation for the reason for this. What is the reason for doing this?

Thanks,

Mike

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

[Tamir Khason]

This is olb naming convention for private variables. In new MS naming
convention you should use m_ as prefix for private members
More information can be found here
http://msdn.microsoft.com/library/de...guidelines.asp
or use FxCop to validate
http://www.gotdotnet.com/team/fxcop/

--
Tamir Khason
You want dot.NET? Just ask:
"Please, www.dotnet.us "
"mike parr" <mp********@yahoo.co.uk> wrote in message
news:Ox**************@TK2MSFTNGP12.phx.gbl...

A few times when looking at code on the net I have seen objects,
variables etc prefixed by an underscore. But I've never seen any
explanation for the reason for this. What is the reason for doing this?

Thanks,

Mike

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

[Scott Allen]

I think the guidlines actually discourage use of m_ when it says "Do
not apply a prefix to field names or static field names."

--
Scott
http://www.OdeToCode.com

On Mon, 5 Jul 2004 11:40:41 +0300, "Tamir Khason"
<ta**********@tcon-NOSPAM.co.il> wrote:

This is olb naming convention for private variables. In new MS naming
convention you should use m_ as prefix for private members
More information can be found here
http://msdn.microsoft.com/library/de...guidelines.asp
or use FxCop to validate
http://www.gotdotnet.com/team/fxcop/

[Bob Grommes]

Nothing magical about it; it's just one of many naming conventions for
private class members. I think the underscore prefix is favored by C++
coders.

--Bob

"mike parr" <mp********@yahoo.co.uk> wrote in message
news:Ox**************@TK2MSFTNGP12.phx.gbl...

A few times when looking at code on the net I have seen objects,
variables etc prefixed by an underscore. But I've never seen any
explanation for the reason for this. What is the reason for doing this?

Thanks,

Mike

[Mike]

I think prefixing any variable in a strongly typed environment simply adds
clutter. I find the convention of capitalizing public members but not
private is much more elegant. Just my opinion.

Mike

"Rakesh Rajan" <Ra*********@discussions.microsoft.com> wrote in message
news:F8**********************************@microsof t.com...

Hmm...I have always been in the opinion that whenever we have an exposed member like a public variable or property etc, we should avoid Hungarian
Notation and prefixes of any type. But for private entities, I would use m_
or a prefix... --
Rakesh Rajan
"Scott Allen" wrote:

I think the guidlines actually discourage use of m_ when it says "Do
not apply a prefix to field names or static field names."

--
Scott
http://www.OdeToCode.com

On Mon, 5 Jul 2004 11:40:41 +0300, "Tamir Khason"
<ta**********@tcon-NOSPAM.co.il> wrote:

This is olb naming convention for private variables. In new MS naming
convention you should use m_ as prefix for private members
More information can be found here

http://msdn.microsoft.com/library/de...-us/cpgenref/h

tml/cpconnamingguidelines.asp

or use FxCop to validate
http://www.gotdotnet.com/team/fxcop/