Thanks.
"Do you really want to send the output to a file named STDOUT?"

Not really. What I was trying to do is have a medium-sized script be able to alternate between writing output to a file or to stdout itself, depending on an option. 

. . .

if (defined($opt{'o'})) {
    $output = $opt{'o'};
    $output =~ s/[\0-\x1f]//g;
    if ($output =~ /^([-\/\w\.]+)$/) {
        $output = $1;
    } else {
        die("Bad path or file name: '$output'\n");
    }
} else {
    $output = '/dev/stdout';
}

. . .

open(my $out, $mode, $output)
        or die("Could not open '$output' for writing: $!\n");

[download]
That way I can use the same print statements for either purpose. I presume there is a better way for all that, however.

In reply to Re^2: Forcing UTF-8 output on STDOUT by mldvx4
in thread Forcing UTF-8 output on STDOUT by mldvx4

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.