Perl's 'if' has to go. It obfuscates needlessly by taking the emphasis of the code away from the conditionals it is trying to highlight. E.g. check out the following typical? code snippet. 

<div class=indent><pre>
if ( $a > $@b and $@b < $c ) {
    for (@b) {
         if (/f(?:o|a)o/) {
              foo($_);
              next;
         }

         if (/b(?:a|u)r/) {
              bar($_);
              next;
         }

         if (/.*/) {
              error($_);
         }
     }
} 
</pre></div>

We can refactor that into if-less code as follows:

<div class=indent><pre>
$a < $@b and $@b < $c and do {
    for (@b) {
         /f(?:o|a)o/ and do  {
              foo($_);
              next;
         };

         /b(?:a|u)r/ and do {
              bar($_);
              next;
         };

         /.*/ and error($_);
     }
};
</pre></div>

We can get rid of the leading and detracting 'if' by replacing it with a suffixed 'and', which is logically equivalent. The funny thing is that I keep saying 'if' in my head when I read the lines. ;) But we do end up with a nice replacement for switch/case in perl (without 'use Switch').

<p>
Problems with this approach include: 
<ol>
<li>Keeping track of do-ending semicolons. 
<li>It'd be nicer if 'and do' was just implied (without a source filter) by 
<div class=indent><pre>
/foo/ {
    foo();
}
</pre></div>
<li>And if...else goes from:
<div class=indent><pre>
if($blah){ 
    derrrr();
}else{
    duhhhh();
}
</pre></div>
to the following not so pretty code:
<div class=indent><pre>
$blah ? do {
    derrrr();
} : do {
    duhhhh();
};
</pre></div>
<li>You keep saying 'if' anyway
</ol>

Arrgh. Why is it so hard to expose logic in code?