Re^2: Code blocks with ternary operator or trailing conditionals

Based on the sage advice in this thread and my own past experience, I have decided on the following (personal approach):

1. For very simple, repetitively used, definitively *scalar* compound statements with if/unless, use the comma operator to allow for single line visually cleaner code. e.g,

$error = "Bad result", next unless defined $result;
[download]

2. Consider using the 'do' statement if the compound statement is still very short and the code will be visually cleaner and easier to read but the operators are non-scalar, so the comma operator can't be used. e.g.,

do{push @results, $item; next} if defined $item;
[download]

Although, that may not be much better/cleaner than:

if(defined $item){push @results, $item; next}
[download]

3. Otherwise use the full-blown if/else alternative

Of course, others will choose other options...

Comment on Re^2: Code blocks with ternary operator or trailing conditionals Select or Download Code

Replies are listed 'Best First'.
Re^3: Code blocks with ternary operator or trailing conditionals by Anonymous Monk on Feb 09, 2014 at 19:32 UTC
Use parentheses for those list-eating functions. `push(@results, $item), next if defined $item;` [download]	[reply] [d/l]