OK... print STDERR "....", ... is not being parsed as a file handle, but as a subroutine call with no brackets... for some reason I thought that required a prototype :-(

The second version, with a () prototype clearly stops that happening.

So the problem is that the subroutine-ness of the modified STDERR is taking precendence over the filehandle-ness -- which is a shame, really.

There are, of course, any many ways of creating a $XXX version of STDERR... what I was hoping for was a way to tweak a FH so that it can appear equally in: print FH .... and p_sub(FH, ....).

Because STDERR is visible everywhere, sub STDERR () { *STDERR } ; placed anywhere very nearly -- but not quite :-( -- does the job without every module needing to do, say, my $STDERR=*STDERR{IO} for itself.

Chris

In reply to Re^2: sub STDERR { *STDERR } -- nearly works ! by gone2015
in thread sub STDERR { *STDERR } -- nearly works ! by Anonymous Monk

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.