Since I started using Perl I've always initialized my variables, many times with undef, but I've seen a lot of CPAN code that doesn't. Maybe it's considered wasteful or uncool?
I usually "declare" my variables on first use - or phrased differently, as soon as I "declare" my variables, I use them. Which, for scalar variables, usually means they immediately get a value (unless I just want their reference). But if they get a value, it usually isn't "undef". I find both 
my $x;

[download]
and 
my $y = undef;

[download]
to be pretty wasteful. I prefer 
my $z = shift;
my $w = $hash{foo};
my ($v, $u) = /pattern/g;
while (my ($s, $t) = each %hash) {...}
while (my $r = <>) {...}
...

[download]

In reply to Re: Perl Style: Is initializing variables considered taboo? by JavaFan
in thread Perl Style: Is initializing variables considered taboo? by ait

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.