I think that to use strict is a good programming practice, like sane variable naming, not using gotos and all of that. Just yesterday I found that debugging script without use strict is long and painful. Consider this typo in a more than 1000 lines of code script: 

my $places_labels = {}; 

# .... about 100 lines skipped

while (my $p = $i->next) {
    $place_labels->{$p->id} = $p->name;
}

[download]

All you need to find such typo is to use strict.

Perl, like Unix, will not stop you to shoot your own foot. You may not use strict if you know what you're doing.

Warnings is similar to strict. If you want to make fast and ugly code that just works and hear no complains from perl - just don't enable them.

In reply to Re: Why use warnings? -w by alexander_lunev
in thread Why use warnings? -w by harangzsolt33

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.