(Trust me to start a row)

IMHO you're both right. Using strict solves so many problems that many questions would never be asked if the poster was using strict in the first place. Witness the number of SOPWs that get half a dozen answers saying nothing but

use strict; use warnings

Its probably always worth putting it on code fragments that perform a complete task such as this.

As to the quoted eval, on this occasion that was left over from a previous attempt to solve the problem, but generally speaking its a bad habit of mine that I need to get out of. Its a bit like one of those words you habitually mispell even though if you stop to think, you know perfectly well what it should be.

VGhpcyBtZXNzYWdlIGludGVudGlvbmFsbHkgcG9pbnRsZXNz

In reply to Re^7: printing a scalar as an array by g0n
in thread printing a scalar as an array by Anonymous Monk

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.