It makes no difference whether you call fputs() from XS code or via a wrapper of an external library function

On win32, at least, there's certainly a difference - in that things get even worse if you call fputs() directly from XS code. The following compiles but there's a runtime error that results in a pop-up telling me that "perl.exe has stopped working". Probably a segfault:
use warnings; use Inline C => <<'EOC'; void foo() { fputs("hello world", stdout); } EOC foo();
I remember having read remarks and caveats wrt to stdio, and advice to use the PerlIO layer instead

Yes (eg perldoc perlclib) ... but the C library function still expects a FILE* (not PerlIO*) as an argument, and it's still going to do an fputs(), so I'm pessimistic about the chances of that being helpful.

Cheers,
Rob

In reply to Re^4: Really, really suffering from buffering by syphilis
in thread Really, really suffering from buffering by syphilis

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.