Ah. You're right. I am, of course, thinking about
readability whitespace, not programmatic whitespace...
This does make it much harder to easily quantify a score for
a piece of code. I am mainly trying to prevent Perl Golf
from simply becoming another Obfuscated area.
Since so much "obfuscated" code is simply normal Perl
constructs with one-letter variable names and no whitespace,
I'd like to see the Perl Golf section emphasize clever,
terse, and readable code, since we already have a section
devoted to unreadability.
Brainbench 'Most Valuable Professional' for Perl