Ok, much more clear now, thanks. Just FYI - the reason why I didn't believe it is because I learned that idiom here ;-) e.g., an article by our own merlyn. Ok, that's not specifically here... but it's a site I only learned about from perlmonks. And the author is rumoured to be reasonably proficient... :-> (Ok, appeal to authority - he could be wrong about some stuff, even in his specialty.) Then, [id://3989;BIT=local *STDERR;BIS=%3B] shows ikegami using it without comment on style (perhaps you just missed them at the time). So I plead educated ignorance - the masters were doing it, so I thought it was a good idea ;-)

Just to continue with the thread drift (though I still would like someone to answer the original questions if they have any help), I'm wondering why they suck. As in, what way? Is it an accidental feature that could be removed from 5.10 or something?

And I found (remembered) another way to kill the messages without redirecting, which is better since it will be much more specific: set the __WARN__ handler to ignore the warning, and that will keep the diagnostics from being hit (since it's a __WARN__ handler, too): 

        my $oldwarn = $SIG{__WARN__};
        local $SIG{__WARN__} = sub {
            my ($msg) = @_;
            if ($msg =~ /utf8_heavy/)
            {
                # do nothing
            }
            elsif ($oldwarn)
            {
                goto &$oldwarn if $oldwarn;
            }
            else
            {
                warn @_;
            }
        };

[download]
And now I don't need to redirect, but I'm still interested in it.

In reply to Re^4: diagnostics, STDERR, and codepage conversions (open) by Tanktalus
in thread diagnostics, STDERR, and codepage conversions by Tanktalus

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.