Ditto! Strongly agree!! :)
Note that Perl Best Practices,
chapter 6 (Control Structures), "Use block if, not postfix if"
argues that postfix-if does not scale as well as block-if, and is harder to comprehend (except in simple cases).
I agree, especially with the scaling argument. Always using block-if has made code reviews more enjoyable for me over many years
because there are fewer changed lines of code to review whenever you just add an extra statement to a block-if
(compared to more violently restructuring the code from postfix-if to block-if).
In chapter 4 (Values and Expressions), "Don't mix high- and low-precedence booleans",
Conway recommends using the low precedence and and or operators for flow of control, for example:
open(my $fh, '<', $file) or die "error opening '$file': $!";
while reserving
&& and
|| for logical expressions (not flow of control) for example:
if ($x > 5 && $y < 10) ...
Following this simple rule over the years has made the code easier to understand at a glance, at least for me.