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


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

Can perl and C have "different" STDERRs on windows?

No. There is only one STDERR on windows and it is always fileno 2. Perl wraps things so that stderr is a variable, but fileno 2 is always the original stderr.

AFAIK, despite claims to the contrary, there is no way to get it to work on win32.

If it was possible it would work already :)

Replies are listed 'Best First'.
Re^6: STDERR going to string
by salva (Canon) on Oct 12, 2011 at 07:43 UTC
    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?

      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?

      :)

      How about you tell me?

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