That's quite cleverly done.

Just, according to -X is -t defaulting to STDIN. So you could spare a word.

2 other alternatives come to mind ...

... iterator

An alternative approach which seems cleaner to me could be to create an iterator which either implements:

sub iter { shift @ARGV } °

or

sub iter {scalar <STDIN>} *

And use it in the loop

while ( ($id) = iter() ) { ... }

... override

Another way could be to override readline (which is the iterator behind <> ) on demand to iterate over @ARGV.

Both ideas untested since I'm posting from mobile.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

°) Could be that you need

sub iter { shift @ARGV //()}

instead, I'm afraid shift will return undef if the array is exhausted.

*) updated scalar


In reply to Re: Getting data from either ARGV or STDIN by LanX
in thread Getting data from either ARGV or STDIN by sleet

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.