58. I keep seeing a variable declared and used immediately just once, and then 200 lines
    later in the same scope they declare the same variable again. Yes, the compiler warns
    them, but if they don't declare it, it won't.  Private variables whose private scope
    within the same function lasts for hundreds and even thousands of lines are dumb. I
    almost envision some sort of aging policy like on perishable food product packaging,
    so every ten lines you don't use a private variable it gets a little more stale,

44. Forbid the Microsoft global/local naming convention.

    I get so ticked when I see a program that has 100 variables
    all named $g_foo and $g_bar, then a function with 50 variables
    all named things like $l_foo and $l_bar.  Took me forever to
    figure out what they were doing.  They were using that to indicate
    scope, instead of using the normal capitalization conventions of:

        our %Hash_of_Functions;
        my  $hit_count;

1. A function should be like a penis, short.

macbook# perl -MO=Deparse,-p -e 'print $a**$b'
print(($a ** $b));
-e syntax OK
macbook# perl -MO=Deparse,-p -e 'print -$a**$b'
print((-($a ** $b)));
-e syntax OK
macbook# perl -MO=Deparse,-p -e 'print $a*$b-$c**$d'
print((($a * $b) - ($c ** $d)));
-e syntax OK
macbook#

macbook# perl -le 'print 5 ** 9'
1953125
macbook# perl -le 'print 5 ^ 9'
12
macbook# perl -le 'print 5 | 9'
13
macbook# perl -le 'print 5 & 9'
1
macbook# perl -le 'print 5 &~ 9'
4

macbook# perl -MMath::Complex -le 'print exp(1)'
2.71828182845905
macbook# perl -MMath::Complex -le 'print exp(1)*pi'
8.53973422267357
macbook# perl -MMath::Complex -le 'print exp(1)*pi**i'
1.12344444904435+2.47526335343173i

macbook# perl -MMath::Complex -le 'print exp(1)**(pi*i)'
-1+1.22464679914735e-16i