That sounds like a great question to me -- ask them how they'd open a file and parse it. It may involve a bit of verbal punctuation, but you can easily wander off into the dis/advantages of using @ARGV and <> as opposed to opening the file manually, perhaps the distinction between while(<>) and while($_ = <>), error handling on the open, and a kazillion things related to parsing (roll-your-own XML parser, or use a module? DOM or SAX or XML::Parser? backslashed quotes in CSV files? when is good enough good enough? etc.)
I work for Reactrix Systems, and am willing to admit it.

In reply to Re^2: Have you netted a Perl Monk or Perl Pretender in 5 minutes or less? by sfink
in thread Have you netted a Perl Monk or Perl Pretender in 5 minutes or less? 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.