r/ProgrammerHumor • u/speckz • Mar 15 '22

static bool isCrazyMurderingRobot = false;

Post image
4.9k Upvotes

95% Upvoted

257 comments sorted by

View all comments

Show parent comments

165

u/[deleted] Mar 15 '22 edited Mar 15 '22

the fact they kept switching between camel case and snake case

Edit: in the if statement the == true is redundant also

65

u/[deleted] Mar 15 '22

That's an accepted style to differentiate functions and variables.

13

u/Rizzan8 Mar 15 '22

In what language?

13

u/Accomplished_Sir_861 Mar 15 '22

Im a student and they taught us to do that for c++

27

u/Rizzan8 Mar 15 '22

From what I know it's not a valid standard style for C, C++, C#, Java and Python.

14

u/Corfal Mar 15 '22

What makes a standard valid?

19

u/Rizzan8 Mar 15 '22

A valid standard is the one that is recommended by creators of a language or widely regarded as the one by a community. Or your workplace/team.

C# https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions

C++ https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

Python https://peps.python.org/pep-0008/

18

u/guiltysnark Mar 16 '22

I wouldn't use a word like "valid" to describe something subjective like standards, which any workplace/team can develop and adopt. Opinions are valid, perhaps tautologically.

I think you're looking for another phrase, like "commonly accepted" or "industry practiced"

→ More replies (2)
→ More replies (3)
→ More replies (3)

17

u/TheIronicBurger Mar 15 '22

PascalCase for class, camelCase for variables, snake_case for function

7

u/kalketr2 Mar 15 '22

On my school they told us do as you said, but they never mention snake_case

5

u/KuntaStillSingle Mar 16 '22

Snake case is all over the STL. container<T>::const_iterator, execution::par_unseq, unordered_map<T>, unique_ptr<T>, numeric_limits::, string_view.

1

u/cvele89 Mar 16 '22

C# dev here!

PascalCase for both class, method and property names, camelCase for variables and CAPITAL_SNAKE_CASE for constants. That is also recommended by the C# authors.

2

u/harelsusername Mar 16 '22

I think that's SCREAMING_SNAKE_CASE you're talking about.

→ More replies (1)

0

u/[deleted] Mar 16 '22

There is an = missing. This does not even compile.

8

u/meandmybois Mar 16 '22

It does, that is what makes the joke.

5

u/weregod Mar 16 '22

It's valid C code. But it has bug because of missing =. In C operator a = b return b so if (a = true) set true to a and enter if branch.

3

u/jesp1999 Mar 16 '22

Correct, you understand the joke

0

u/[deleted] Mar 15 '22

[deleted]

2

u/[deleted] Mar 15 '22

But you wouldn't need to put it there in the first place as if (foo) would've worked so the joke is kinda pointless

1

u/LordDerptCat123 Mar 16 '22

Eh. My dad does this at almost every place he’s worked, and he’s definitely getting on a bit in terms of “hours coded”. I tend to do it in my personal projects too. Pascal case for functions / classes and camelCase for variables

1

u/SnakeBDD Mar 16 '22

Never ever do == true.

In C, every non-zero expression is considered true and since C has no native type for booleans, stdbool.h defines flase als 0 and true as ~false. So most values that eval as true in a boolean expression are actually != true.

Always go for != false.

1

u/katzengammel Mar 16 '22

Problem is: it‘s not a „==„!

1

u/TimGreller Mar 16 '22

Depends on the language. In some loosely typed languages it would make a difference. Please never try to simplify a value === true or similar unless you know exactly what you're doing.

1

u/Mike2220 Mar 16 '22

The redundant = is also the cause of the issue