Nothing wrong with forced advancement as long as it's slow. If we had people happily writing Perl 5.005 code (or worse, imagine Perl 4), we would have people trying to keep up with the language and seek out new features. Stagnation = death. I don't want Perl to be like awk. No one does.

Also, more On-Topic: This topic isn't remotely about our being considered harmful, it's about your sysadmin being considered harmful. Our is not as good as my due to the principle of "smaller scope" is better, and I write code all day without it -- but I note a recent trend to tack "considered harmful" onto the end of meditations to appear like a certain famous computer science guy, and that's just silly.

In reply to Re^3: Use of 'our' considered harmful by SpanishInquisition
in thread Use of 'our' considered harmful by DrHyde

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.