Am I the only one who prefer the explicit condition syntax?

[as96]

I mean I prefer writing:

if(lol == false){ }

instead of:

if(!lol){ }

Am I weird?

[burnttoastnice]

snip

 

There's several ways to do the same thing in code so nahh bruh you good. I use a mix of them tbh. Especially in PHP where I have to use === to detect function errors (file_get_contents not being able to open the file etc) because the devs haven't heard of a try-catch

[manikyath]

i actually rarely use booleans, if i encounter stuff like this, its usually catching the return of a function.

[LukaP]

I prefer the implicit way, because simply its faster to write :'D

 

also i prefer

if (!lol){   code;}

to 

if (!lol){code;}

[ICantThinkOfAnyGoodName]

It is overly complicated IMO and is also slightly less efficient in terms of computing power IIRC, although that won`t ever make a real world difference.

[Shoob]

Explicit makes it more easy to read and if I prefer using it when explaining stuff to total beginners who are seeing an if-else statement for the first time.  :lol:

Most of the time I go for the implicit way because it saves some typing. (is this the way it's called?)

[SteveGrabowski0]

I prefer using error codes myself

 

if (8==D) {   error("aw fuck");}

[Sauron]

It's the same thing, but why type 12 characters when 4 will do?

 

also, !lol can also mean lol does not exist yet, whereas the implicit comparison will give out error if it can't find the value of lol. Depending on what you're doing it may be a problem.

[Nuluvius]

Out in the real world the common mentality is to face palm when one encounters explicit evaluations...

[madknight3]

Everyone has their own preferences for how they write code. The most important thing is to be consistent across the whole project. If you are working with/for other people, everyone should be following the same guidelines and you may not get to do everything the way you prefer. What you decide to do in your own personal projects is up to you.

[Crabtr]

I prefer implicit. It's nicer looking, makes the code easier to traverse, and it allows you to much more easily hit those 80 character line limits. That being said though, I'm not going to really complain about being explicit if being implicit would be against the style guide; consistency is much more important.

 

 

also i prefer

if (!lol){   code;}

 

No space between the conditional and the open curly brace? You heretic! 

[Nuluvius]

I prefer implicit. It's nicer looking, makes the code easier to traverse, and it allows you to much more easily hit those 80 character line limits. That being said though, I'm not going to really complain about being explicit if being implicit would be against the style guide; consistency is much more important.

 

 

No space between the conditional and the open curly brace? You heretic! 

 

Oh no don't get me started on the brace positioning because I hate all of them so far. It's Allman or it can go to hell as far as I am concerned. Sod consistency because if I see the other in anything other than JavaScript I change the consistent style.

[Egad]

unless something

{

    foo

}

[Stuff_]

Honestly it doesn't matter how you code, unless you're at a business. In that case, you must write your code based on their syntax. 

[as96]

Honestly it doesn't matter how you code, unless you're at a business. In that case, you must write your code based on their syntax. 

When I work with other people I adapt to their syntax, but I'm talking about a personal preference on my own stuff.

[Tigerbomb8]

I prefer to be verbose when i know a beginner is going to be reading the code, but all other times my IDE bitches at me so i use the shorthand.. 

[Philosobyte]

It is overly complicated IMO and is also slightly less efficient in terms of computing power IIRC, although that won`t ever make a real world difference.

Both formats will perform the same way, IIRC. The compiler will optimize it in a way that they end up having the same underlying bytecode. 

 

I prefer implicit because after a while of programming you get used to seeing it and the logic is just as clear as the explicit form. 

[madknight3]

So how far do you take the explicit comparison?

if ((lol == true || lmao == true || rofl == true) == true) {}if ((a < b) == false) {}if ((i%2 == 0) == true) {}

[fizzlesticks]

Both formats will perform the same way, IIRC. The compiler will optimize it in a way that they end up having the same underlying bytecode.

Depends on the language and compiler of course. 

Doing 

s = Falseif s == False:    print(1)

in Python will be slower than doing

s = Falseif not s:    print(1)

[as96]

 

So how far do you take the explicit comparison?

Usually over 2 conditions I use implicit.

 

I know I'm weird...

[madknight3]

Usually over 2 conditions I use implicit.

 

I know I'm weird...

 

Now you're just being inconsistent

[Stuff_]

When I work with other people I adapt to their syntax, but I'm talking about a personal preference on my own stuff.

I know, that's why the first 6 words of my sentence say it doesn't matter.