I've a c library thats been wrapped by SWIG. This is very handy in allowing me to make use of these routines in my scripts but I think I've come across a problem.

The funtion (swig wrapped remember) can send information to STDOUT. I want to take this and redirect STDOUT to various sockets. To do this I've tried a number of differeent methods including capturing STDOUT using IO::Scalar and tie, binding STDOUT to the socket using fileno and open STDOUT, ">&=$fd"; and so forth all to no avail.

I think I determined that the problem is that SWIG isn't actually piping its STDOUT back into perl's STDOUT. So I can do anything I like STDOUT in perl and it will have no effect because these environmental changes are not being inherited by the function/c API.

Does this sound likely? If so can anyone think of a way to get around this that doesn't involve rewriting the API?

Chris

In reply to STDOUT and SWIG by rapier1

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.