As I understand it, your first input call (w/ <>) is slurping up ALL your data, so that the next read (using <STDIN>) is reading nothing - that's because the first diamond is in list context, so everything gets read until EOF.

Once again, that's just my opinion. I could easily be misunderstanding your problem, but I hope that helps somewhat.

Somewhat unrelated note/Update: It's been said a few times around here that <> isn't a good idea for reading from STDIN unless you're sure you just want the unadorned diamond (which will read in from the files listed in @ARGV and not STDIN). If that's not the case for you (I can't tell from your code), then I'd suggest switching the call, for both clarity and safety.

His Royal Cheeziness

In reply to Re: STDIN following on? by CheeseLord
in thread STDIN following on? by tfrayner

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.