Re: Using stderr from Inline::C: (part deux)

[hdb]

This might not be of great help to you, but under Win32 strawberry-perl 5.16.3.1 #1 Tue Mar 12 12:12:07 2013 x64 the following code works:

use strict;
use Inline C => <<'__C__';
#include <stdio.h>
void test ( ) {
  char buffer[] = { 'x' , 'y' , 'z' };
  fwrite (buffer, 1, sizeof(buffer), stderr );
}
__C__
test( );

Reading your old thread, it looks to me that the root cause of the problem was a mismatch of compilers. So one solution could be to either change compilers or re-compile Perl with your preferred compiler.

[BrowserUk]

the root cause of the problem was a mismatch of compilers.

Kinda. Sorta. But not really.

I::C code is compiled to a runtime linked dll. There is nothing fundamentally wrong with using multiple different CRTs within different dlls in the same process. (provided you don't try to mix'n'match by (say) mallocing with one and freeing with another.)

Indeed, this is (so far; but I've been doing it for a good many years) the only real problem I've encountered with using a different compiler for building modules and I::C stuff, than was used to build the AS perl I use.

The problem is that the Perl headers pull in a shitload of the PerlIO crap regardless of whether the code being compiled uses it or not. And it is that PerlIO crap that is screwing this up.

So one solution could be to either change compilers or re-compile Perl with your preferred compiler.

Neither of those is an option. It has to be AS perl. The compiler AS use is no longer available; neither is (their) source for the build of Perl I need for this.

But thanks for your reply.

[bulk88]

http://osdir.com/ml/lang.perl.perl5.porters/2006-02/msg00408.html Use NO_XSLOCKS to stop Perl from header hooking clib io.

[BrowserUk]

Thanks. That looks interesting. I'm just not yet sure if it is possible to use with I::C given that it prepends the headers to your code, there is no way I can see of defining that before the headers get included.