Using '&&' instead of 'if' for single instructions

Question

I'd like to know if there are any problems with doing this:

($this->debug)
    && print "We're debugging right now";

instead of this:

if ($this->debug)
    print "We're debugging right now";

To me, it's just a style thing. Does it do exactly the same thing?

I think one of the most important code-metrics is readability. How well can a stranger take over your project? — Lauri Elias, Jan 04 '15 at 15:16
It's the same of `if ($this->debug && print "We're debugging right now")`. They do the same thing, the only difference is that it takes me a moment to realize what it do. — Federkun, Jan 04 '15 at 15:18
I understand that completely - always have. All I'm asking for is any caveats... It's only for single instructions. — Mike Rockétt, Jan 04 '15 at 15:21
I don't think that downvoting him is fair. His question is a valid one. — Madara's Ghost, Jan 04 '15 at 15:24

score 7 · Accepted Answer · answered Jan 04 '15 at 15:22

Please don't. This is horribly unreadable. And it starts innocently enough, soon other "clever" developers would come and invent more "clever" ways of using this && operator to avoid those "horrible" ifs.

Please... Don't.

Functionally, yes, they will work the same.

score -3 · Answer 2 · answered Sep 28 '17 at 13:14

The shorter the code (up to a point!) the better.

You should tell your code what to do. You should not be asking your code, if you are allowed to tell it what to do. Your coding, like love, should be Unconditional!

Need more arguments?

&& is better:

fewer chars to type
fewer lines of code
lower cyclomatic complexity
if's are closer to configuration than logic

Conditionals aren't always bad, but they can be (and frequently are) abused. source

Some clever developers built-in similar solution directly into PHP, @Madara Uchiha the null coalescing operator ?? i.e. was introduced to PHP.

Functionally they will produce the same result. But one (&&) says you are a quality programmer, the other (if) says you are doing it as a side hussle.

Stop being scared of your code.

Be proud of your code.

Using '&&' instead of 'if' for single instructions

2 Answers2