It's costless to replace == with >=...

I disagree. It's extra code to read, to understand, to be executed, and to maintain. It's very little in this case, but I think it's an awful reason to do something because "it might be needed in the future."

The best way to make your code extensible is not to add in features you think you might want someday. The best way is to write simple, readable, testable, and simple (yes, doubly simple) code that does what it needs to do and no more. If you fall into the trap of thinking that you need to plan for things you can't foresee, you'll be hampered in your ability to make changes. "I can't change this code because it plans for a case I might need down the road, and I've already written it."

I don't think of that as "defensive programming" but rather fearful, packrat programming. In my mind, defensive programming is checking error codes and boundary conditions. (You could also argue that, given my preference above, it's not adding things that don't have an immediate benefit, but that's a bit of a stretch.)

In reply to Re: Defensive Programming by chromatic
in thread Defensive Programming by George_Sherston

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.