What do you think?

[machowski lukasz]

i hate prefix "_", because code is not intuitive and reading this is very uncomfortable. I'm programing in c#. Regards Łukasz

[Jon W]

I Like them! :rose: Why? I'm a VB.NET developer... to write none language dependent code is like coding to interfaces instead of implementations ;P What do I mean? Well to easily convert / write / use code from BOTH c# and VB.Net "_" simplifies a great bit... Mainly because vb.net is not case sensitive. I find the "_" char the least disturbing in reading / skimming through code. The m_ prefix i dislike the m_ prefix as I consider it outdated; as far as I know the m stands for member, and if I want to now a class member I take a look in the Object browser, or use the "Me" (this in c#) ex: Me._myFieldName therefore in my opinion -> m_ adds "nothing". As the previous post states, the _ is used for private members and therefore encapsulated by the class and you work with the public properties / methods instead i.o.w not that big of a problem (in my humble opinion) in contrast to language independence.

[David Veeneman]

I hated it at first, but got used to it. I use 'm_' for member variables, and 'p_' for property variables. I still hate the underscore by itself, like '_this'.

David Veeneman www.veeneman.com

[realJSOP]

I'm not missing. I am working on a series of articles for CP since all the local roads are closed and I can't get to work. :) I only prefix compiler definitions with underscores, like so:

#define _USE_THIS_MSG_ WM_APP+1

I don't prefix variables with underscores, and don't embed variable names with underscores beyond the gratuitous "m_".

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

[Aaron VanWieren]

Mark Nischalke wrote:

Because we've always done it that way

Oh no, the dreaded "We have always done it that way"!!! :-D

[Aaron VanWieren]

Mohamed A. Meligy wrote:

class library developer guidance.

Just curious, but do you have a link for this. Whenever I look for this, I find a gazillion different styles being used in Microsoft example code.

[neffc]

I am very agreeable with the underscore since it takes advantage of Intellisense for seeing my private/protected fields quickly. It should not matter what you name a field because it should always be accessed through a property. What I would like to hear some opinions on is the naming of User Interface controls such that I don't want my default event handlers looking really crazy i.e. do you: btnValidate buttonValidate validateButton (something else) cneff78

[lotuspro]

I appear to be in the minority here but I *always* use the underscore to prefix private members. I do this for 2 reasons: 1.) As noted by another commentor, I consider the m_ wholly antiquated and sorely reminiscent of old school VB 2.) whenever I write a new class, especially in something like a data layer, I name my members the same as my field names in my database, but of course I have Properties also and then should also have the same name, so I end up with a simple _fieldName notation. It makes for eacy copy & paste. I'm right, that is all ;)

[mc42]

No, it's not part of Hungarian notation. Hungarian notation was a programming practice that prefixed variables with the type (for example, iLoopCounter, dSalary, etc). The m_ or just plain _ prefix is a method to be able to use a good name in the class and as parameters. class myClass { string _name; public bool myFunction(string name) { _name = name; } } as an example. I think the m_ came into play when class global variables were directly accessable as it made it easier to read (nameClass.m_name is easier than nameClass._name), but with the shift to treating local variables as private and providing accessors, the m_ isn't as necessary and using the _ prefix preserves the "good" names and makes it easier to translate code between languages that are/are not case sensitive.

[eddlsda]

Both Hungarian and use of underscores have their roots in C espeically those of us that lived in a flavor of unix. Amongst the development community I worked with in the late 80s, we used underscores to avoid name collisions between file scope and local variables. We used Hungarian notation to add type and pointer details to variables especially those defined as extern. With the advent of Object-Oriented programming and the concept of encapsulation, the need to know the type essentially became less useful and besides, as those that lived through maintenance of such code, misleading or erronous. From what I have seen, the use of underscores or prefix styles is usually done to avoid name collisions between class field/member declarations and parameter names that might be used in methods or constructor parameter lists. My opinion is that there are better means to do this by either avoiding the collision or use of a qualifying this. to scope to the correct member. Hence, I do not find use of prefix or underscores useful but can live with them if used consistently.

Don Eddleman Principal Enterprise Architect Healthways

[BC3Tech]

i vote m_ here.

[Stick]

Actually better to use IN and OUT as you will find MS doing. Forgot the techie name for this syntax in signatures, but the only reason MS is doing it is they are going for interoperability with .NET languages.

[drdavef]

I used the m prefix when using VB6. Now with VS2005, I much prefer the _ and have also stoped using str, int, prefixes also. Much more like the Java mode for naming object. David

[ednrgc]

I usually name the private member in lowercase, and the Properties to access them in CamelCase.

[R Ziak]

Search MSDN for naming conventions.

[MSBassSinger]

>Do you use/like the "_" to prefix private members? My habit is to use m_ for module level variables. I never make them public. If I want to expose its value, I use a property to get or set it. I use no prefix for variables whose scope is within the method. I also use a 3 letter prefix for the data type, e.g. strName, m_lngCount, etc. It is not the only way, but it is a way I like, it is readable, and I see no reason to change. I never saw a reason to simply use a "_". I remember the days when processor cycles and memory (RAM and disk) were at such a premium that code was cryptic. Those days have been gone for decades, so I saw no reason not to use more human readable names. JD Waleska, GA

[DavidNohejl]

We call' em fields.

---

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

[Phil Harding]

dnh wrote:

We call' em fields

Luddite :)

Phil Harding.
myBlog [^] | mySite [^]

[Member 96]

It took me a *long* time to break that habit when I moved to c#.

[sstring]

For those who are interested, I created a poll to settle this once and for all (:laugh:). Variable Naming Conventions Poll[^] BTW: The site is new - Any feed back would be greatly appreciated. Thanks! Steve