While short identifiers like $gotit are probably ok, use underscores to separate words. It is generally easier to read $var_names_like_this than $VarNamesLikeThis, especially for non-native speakers of English. It's also a simple rule that works consistently with VAR_NAMES_LIKE_THIS.

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

And from just below your quote in perlstyle:

  o   You may find it helpful to use letter case to indicate
      the scope or nature of a variable. For example:

          $ALL_CAPS_HERE   constants only (beware clashes with perl va
+rs!)
          $Some_Caps_Here  package-wide global/static
          $no_caps_here    function scope my() or local() variables
[download]

My point is simply that what hardburn said was the general way is not the general way.

Seeing how perlstyle comes with every perl distribution, i'd agree with hardburns presumption regardless of facts to the contrary.

update: whoops, oh well

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"

I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).

** The third rule of perl club is a statement of fact: pod is sexy.