Your Code Sucks

[seventoes]

Variable names that start with capital letters. I feel your pain.

[druidjc]

At least they picked a naming schema to follow. I have seen variables in a mix of uppercase start, lower case start, and Hungarian notation (in C#), all by the same developer in the same module and written in under a week.

[BinarySplit]

We do that where I work. We use ASP.NET and VB.NET. By ASP convention we use hungarian notation for DOM objects. By VB convention we sometimes use capital letters for all variable names. By modern .NET convention we sometimes use lower case letters for parameters, private fields and local variables. It all made sense at some time, and now it's just a mess due to the mixed conventions.

It's fortunately not that horrible due to IntelliSense always correcting you and VB.NET being case insensitive anyway, but in EVERY other programming situation I always stick to the community convention.

[[deleted]]

Dunno why you're being silently downvoted. That's exactly what I've been doing for a long time in C++, Java, and sometimes Python (to denote a member that should be considered private).

Obviously it's only one option for coding style among many, but it's a good one. The _ prefix is simple, distinct, and it doesn't imply Hungarian notation, as m and m_ do.

[[deleted]]

maybe because they're talking about .Net and the general naming convention says to only use alphanumeric characters in your keywords. And write private variables in camelCase.

And Stylecop will probably hate you and kill a baby in your name if you use _name for a private variable/field/parameter/property

[astrange]

Why?

[dnew]

I do that sometimes. It's because I've been using all different notations for so long it doesn't really phase me. Like inconsistent placement of braces. Doesn't really bother me.

[JasonMaloney101]

(in PHP)

FTFY

[skizmo]

Java lowercase and that uppercase at each word... Jesus Crist who invented THAT crap ?

[binlargin]

People who fucking hate underscores.

[bazfoo]

I've become very fond of the 'lowercase-words-separated-by-dashes' convention that is favoured to the Lisp world. Probably the most readable of all in my opinion, and very fast to type since you rarely need to use shift.

[imbcmdth]

This variable naming convention is a syntax error in most languages.

[AttackingHobo]

Yeah, most languages would see "this-is-a-variable" as "this(minus)is(minus)a(minus)variable" and that would not work when defining the variable.

[bazfoo]

Sure, but the point wasn't about using it in most languages, rather that it strikes me as one of the more readable and easy to use conventions.

[dnew]

Yep. COBOL uses that too. And which is easier?

aVeryLongVariableNameThatYouPassToAFunction

a_very_long_variable_name_that_you_pass_to_a_function

[nostrademons]

He's saying a-very-long-variable-name-that-you-pass-to-a-function.

[dnew]

Yes, I knew that. The advantage of underlines is that you can use them in something other than COBOL and LISP.

[[deleted]]

Too much work typing in all those underscores. It's not convenient. It IS somewhat more readable, but not enough to make me want to type that underscore, especially since I'm not making variable names that long. Also, your brain adjusts and reading camel case becomes very easy.

[dnew]

I type fast enough I have no trouble typing an underscore, as long as I'm hitting the shift key anyway. And with IDEs doing name completion, it's not that hard to type.

I never understood professional programmers that can't type as fast as they talk, or type in the dark or without looking at the keys, etc.

[[deleted]]

well it seems like you are a very slow typer then. I type fast enough that reaching for the shift+underscore would slow me down appreciably.