http://www.perlmonks.org?node_id=930926


in reply to Re^5: STDERR going to string
in thread STDERR going to string

But then, why after redirecting STDERR, fileno(STDERR) is still 2? is it cheating?

And why the Inline::C does example does not work even when the perlio.h redefines C stderr to point to some variable inside the perl runtime?

Replies are listed 'Best First'.
Re^7: STDERR going to string
by BrowserUk (Patriarch) on Feb 17, 2012 at 07:29 UTC

    The source of the problem *is* perlIO. Not the underlying Windows CRT calls. With the PerlIO #defines in place, you cannot even do:

    fprintf( stderr, ... );

    Without perl crashing in a heap around your ears.

    However, if in your XS code, you #undef stderr to bypass the ridiculous PerlIO redefinitions, things begin to work. But you also have to defeat all the other pointless PerlIO redefinitions.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?

Re^7: STDERR going to string
by Anonymous Monk on Oct 12, 2011 at 08:35 UTC

    :)

    How about you tell me?

    If I were curious I would ask perl5-porters :)