Soon-to-be-released Devel::Comments has a build_requires (test) dependency on IO::Capture and friends. Other stuff in the pipeline has the same or a stronger dependency.

IO::Capture::Tie_STDx 0.05, which does the heavy lifting for various IO::Capture modules, has two bugs. It incorrectly handles say(); and it fails to implement a TELL() method.

I emailed the author, Mark REYNOLDS, over two months ago; no reply. Granted, I haven't yet made a concerted effort to contact. Given, I should. I needed these bugs fixed immediately so, that's what I did.

I have written two modules, IO::Capture::Sayfix and IO::Capture::Tellfix. Each, on load, makes a quick test to see if the corresponding bug has been fixed in the currently loaded ::Tie_STDx; if so, it does nothing; else it fixes the bug on the spot. ::Sayfix redefines PRINT(); ::Tellfix defines TELL(). This approach is intended to play well with the existing version of ::Tie_STDx as well as any future version in which either, both, or neither of these bugs are fixed.

Before writing ::Sayfix, I patched a copy of the existing ::Tie_STDx. I was told by other Monks, in no uncertain terms, that even to install such a thing locally was to ask for trouble.

Seeking some direction on how to proceed. One or more of:

  1. File formal bugs on RT.
  2. Ping REYNOLDS heavily via email and any other available route.
  3. Prepare a formal patch to ::Tie_STDx.
  4. Open a GitHub fork for ::Tie_STDx.
  5. Package ::Sayfix and ::Tellfix as (one module? two modules?), together with appropriate POD, Build.PL, etc. and upload to CPAN.
  6. Open a GitHub repo for the *fix modules.
  7. Package the *fix modules together with those projects that depend upon them and make them part of their installations.
  8. Other: ________
Note: Contents may change.

In reply to Dealing with IO::Capture bugs by Xiong

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.