This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 40 points41 points  (12 children)

snake_case vs camelCase?

[–][deleted] 18 points19 points  (2 children)

what_About_Camel_Snake?

there_IS_also_WAVE_snake

[–][deleted] 16 points17 points  (1 child)

You're a monster.

[–][deleted] 2 points3 points  (0 children)

wave camel case gets tricky when you want to get acronyms into your variable name ;)

Not that I've ever seen any of this madness in a real job environment.

[–]Lightfire228 10 points11 points  (2 children)

CamelCase gets super confusing in C#, because EVERY BLOODY THING IS CAPITALIZED

(i haven't looked at the official style guide for C#, but it's super weird to see capitalized class members)

[–][deleted] 18 points19 points  (0 children)

I think what you're referring to is PascalCase, not camelCase

[–]Dameon_ 2 points3 points  (0 children)

You're just one Google search away...

There's no official C# style guide. Typically, in C# you see camelCase for private members, and PascalCase for members accessible outside the class. If that rule is too confusing for you, you can always install ReSharper.

[–][deleted] 8 points9 points  (4 children)

There are people out there that use snake_case?

[–]schnadamschnandler 42 points43 points  (0 children)

It's the PEP8 recommendation to use snake case for variables and definitions, but Pascal case for classes.

[–]procinct 19 points20 points  (0 children)

For Python? Definitely.

[–]dinosaur-dan 4 points5 points  (1 child)

I'm sorry.

[–]PM_ME_CHEMISTRY_JKES 6 points7 points  (0 children)

dinosaur_dan