What you are refering to is the difference between compile-time errors and run-time errors. use strict does not catch run-time errors. Matter of, fact, the only thing that can catch run-time errors is a pair of eyes - someone else's pair of eyes usually sees it before your pair of eyes!! :D (figuratively speaking)

Good example, Perl will happily compile and run this without complaining in the least - bonus points for an explanation why: 

foreach (@list) {
  $conn-do("insert into foo values($_)") || die;
}

[download]
when i really meant this: 
foreach (@list) {
  $conn->do("insert into foo values($_)") || die;
}

[download]
So, DO rely on strict to check for the things that strict can verify. It's your brain that you shouldn't rely on - mine get's me in trouble every time at least ;)

jeffa

In reply to (jeffa) Re: sometimes use strict isn't enough by jeffa
in thread sometimes use strict isn't enough by coolmichael

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.