I created a fork bomb by accident. 
for my $i (@list) {

    my $status = fork();

    if ($status < 0) {
        # error condition

    } elsif ($status = 0) {
        # in child

    } else {
        # in parent
    }
}

[download]
The bug is a typo. The conditional: ($status = 0) Should be: ($status == 0)

As soon as I saw it I thought "I know better. I should have put the constant on the left" like: (0 = $status) because it will produce an error instead of a conditional that fails.

I suppose I could have used ranges and left zero to be the default. 
  if ($status < 0)
  elsif ($status > 0)
  else

[download]

What habits do you have to prevent making mistakes when you write code?

In reply to What habits do you have to avoid introducing bugs? by superfrink

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.