Redirecting is possible, but is very likely to create buffering issues. Printing after every line can cause possible problems if either there are buffering issues, or if 2 questions are asked in a row. There is also the possibility that at some point it asks a non-yes/no question, in which case you need more logic. Try my suggested hack, if that fails you should be able to see the question it trips up on.

About using an API, I know what legacy code can be like but you still can do it. Just put a well-named function call in that line, and go off to write your function somewhere however is best. Then the legacy code is no worse, and you're free to write that function however you see best.

In reply to Re^3: IPC::open3 obfuscification by tilly
in thread IPC::open3 obfuscification 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.