I should point out that the code in the eval will be unknown, not wirtten by me no idea what's in it. Also, I have already dupped STDERR to STDOUT as well.

UPDATE: Clearly dupping STDERR it is not right, fixed that I am now trying to open STDERR to the same file as STDOUT in the same way (though one is > and the other is >>)

UPDATE 2: I should also note that I'd rather not use IO::Scalar as it's not standard even in 5.6.1. Maybe I'm just asking for too much? But it seems that the only thing preventing a reasonable solution is the warning about using the filehandles once. And I'd like to understand it before I do local $^W=0; 

-- 
perl -p -e "s/(?:\w);(<A HREF="/index.pl?node=st&lastnode_id=3333">st<
+/A>)/'\$1/mg"

[download]

In reply to Re: open(INPUT, "&lt;INPUT") gives INPUT opened only for output by belg4mit
in thread codeopen(INPUT, "&lt;INPUT") gives INPUT opened only for output by belg4mit

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.