If I seem to be advocating don't check for errors, then you fail to understand what errors you should be checking for.

Since you prompt me on this I will say: Check only for errors you can reasonably expect. For example, if you spend six months writing code that caters for porting to some non-forkable environment where undef will be returned, makes sure that it works in a VMS or mainframe environment, or iOS and android, sure you can persuade yourself that you are somehow being superior, but if your boss only asked for it to work on win10 or linux, you are wasting your employer's money!

One world, one people

In reply to Re^7: Doing every X seconds by anonymized user 468275
in thread Doing every X seconds by dideod.yang

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.