in reply to 5Re: "use strict;" woes
in thread "use strict;" woes

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.

Replies are listed 'Best First'.
Re: Re: 5Re: "use strict;" woes
by PodMaster (Abbot) on Oct 15, 2003 at 00:29 UTC
    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.

[reply]
      I *was* quoting perlstyle which explicitly says in the quote I gave that globals be of the form $Some_Caps_Here, whereas hardburn stated globals should be all caps, which perlstyle reserves for constants. Perhaps the OP means his globals to be constants, but the OP and hardburn only refered to globals. sheesh, a little pedanticism goes a long way :)
[reply]
[d/l]

In Section Seekers of Perl Wisdom