Does this include POD put before subroutines?

Yes it does. That was exactly what I was aiming it. Whenever I have to go through a file that alternates POD, subroutine, POD, subroutine, I find it very hard to find my way around the code.

I also think that it's rare you want the documented function to appear in the same order in the manual page as that you happen to have them in the file.

Is there any execuse for not doing "use constant ..."?

Most certainly. It's easier to interpolate $CONSTANT than CONSTANT. And $CONSTANT will not fall victim to autoquoting (left of a fat arrow, or as a hash index), while CONSTANT might if you aren't careful.

Cuddled?

"Cuddled elses" is a term from perlstyle. It means:

    if (condition) {                                                  
+         
        code
    } else {   # This else is cuddled.
        more code
    }
[download]

This is K&R style. With uncuddled elses, you align the else with the if and the closing braces. There's a lot to say for K&R style though, it strengthens the fact that else doesn't start a new construct, but is part of the if, and it will save a line.

Abigail