Name Conventions

peterchen

Most important: Whatever you use, use it consistently. Second most important: What does your companies coding style guidelines say? Third most: Many platforms are associated with a "default style". - see Colins post

Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify!|Fold With Us!

Ennis Ray Lynch Jr

camelCase for members, variables, and parameters. PascalCase for methods, Events, and Properties. Of course we all know that Java style is far superior I don't know why the folks at MS tried to dictate a different style.

File Not Found

Christian Graus

I thought we were talking about methods. For variables and properties, I do the same. upper/lower case differences are not enough to be CLS compiant, because VB sucks.

Christian Graus - C++ MVP 'Why don't we jump on a fad that hasn't already been widely discredited ?' - Dilbert

Tim Craig

Ennis Ray Lynch, Jr. wrote:

I don't know why the folks at MS tried to dictate a different style.

Because Not Invented Here is alive and rampant at Microsoft. They just, a priori, know what's right.

The evolution of the human genome is too important to be left to chance idiots like CSS.

Vasudevan Deepak Kumar

http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html[^]

Vasudevan Deepak Kumar Personal Homepage Tech Gossips

Paul Selormey

Christian Graus wrote:

CLS compiant, because VB sucks.

Wrong, it is because CLS==language independence, a feature it boasts off over Java bytecode. BTW, it is your perfect C# compiler that will complain. If you write and consume your components only in C#, just remove the CLS compliant attribute, and stop blaming VB for your bugs ;P With love, Paul.

Jesus Christ is LOVE! Please tell somebody.

Eytukan

Hockey wrote:

I typically use an prefixed underscore

Element names starting with an underscore (_) are not part of the Common Language Specification (CLS), so CLS-compliant code cannot use a component that defines such names.^:->

Code-Frog:So if this is Pumpkinhead. Time for him to run and hide. It's an interesting thought really.

Aryo Handono

How about in VB ? ;P

"Courage choose who will follow, Fate choose who will lead" - Lord Gunner, Septerra Core "Press any key to continue, where's the ANY key ?" - Homer Simpsons Drinking gives me amazing powers of insight. I can solve all the worlds problems when drunk, but can never remember the solutions in the morning. - Michael P Butler to Paul Watson on 12/08/03

Duncan Edwards Jones

Use GetValue() in VB - ....although if you are a proper VB programmer you'll probably be a bit more explicit about what the Value is...

'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd

NormDroid

... or even just Value for accessing a property.

We made the buttons on the screen look so good you'll want to lick them. Steve Jobs

DavidNohejl

I think that applies to public members/fields only.

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

Christian Graus

Paul Selormey wrote:

Wrong, it is because CLS==language independence, a feature it boasts off over Java bytecode.

True -and to make it language independant, they needed to make it case insensitive. Which languages are case insensitive ?

Paul Selormey wrote:

BTW, it is your perfect C# compiler that will complain.

Of course it will. The VB.NET compiler is too stupid to see a difference between var, Var and VAR to start with.

Paul Selormey wrote:

just remove the CLS compliant attribute,

I've been known to do that, actually

Paul Selormey wrote:

and stop blaming VB for your bugs

ROTFL - you're obviously kidding around, but either way, I think a language being case insensitive is just plain dumb. It's obviously a 'feature' added to VB.NET to make it easier, it's not something that has a real advantage beyond that.

Christian Graus - C++ MVP 'Why don't we jump on a fad that hasn't already been widely discredited ?' - Dilbert

Steve Hansen

However, an underscore in any other position in an element name is CLS-compliant.

So it only matters for public properties/methods which I don't think they do. Just for fields like I do.

DavidNohejl

Steve Hansen wrote:

However, an underscore in any other position in an element name is CLS-compliant.

I understood this as _element is invalid, but element_, my_element etc are OK.

Steve Hansen wrote:

So it only matters for public properties/methods which I don't think they do.

Agreed.

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

Jonas Hammarberg

Be consistent. If maintaining, adapt (even if it's wrong -- or rewrite the whole lot, there are beautifiers). As you gather wisdom, you will develop your own style;) I heard about a company using beautifiers. Many of the coders had their own style and instead of going to war over brackets and spaces the company decided on what style the code should comfirm to when checked in. What style each and one of the coders used when working on their parts was irrelevant. rgds /Jonas

Gary Wheeler

OMG. There's another one us out there that uses this convention. I'm not alone anymore. (sniff)

Software Zen: delete this;

subai

i used to (and i like to) use prefix underscore in private members but it's not recommended by the boss(it's forbidden) :(

I Wish the Life Had CTRL-Z

Pete OHanlon

I do, but only for private members. As has been written elsewhere, underscores on protected members will raise errors because they are not CLS Compliant.

the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.

Gary Wheeler

Our naming conventions are something like this: PascalCase for public classes, members, 'file' static values, and globals. _PascalCaseWithLeadingUnderscore for private/protected classes and members. camelCase or lower_case_with_underscores for local variables. ALL_UPPER_CASE_FOR_DEFINES which are required to be manifest constants only. If we ever start doing .NET development (we're currently a C++/MFC house), we may need to modify our conventions. .NET enforcing a naming convention is annoyingly reminiscent of the Ada development tools I had to deal with back in the late 80's. They were equally obnoxious about requiring adherence to some academic's notion of proper programming technique. I am of the "Grady Booch must die" programming school, myself :|.

Software Zen: delete this;

Gary Wheeler

Tim Craig wrote:

They just, a priori, know what's right

How does an 800 pound gorilla write software? (wait for it) However he likes.

Software Zen: delete this;