comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks