Steffen Mueller (smuel...@cpan.org) writes:
Check the C code generated by xsubpp. Then insert ludicrous amounts of
printf()'s into the code that comes after the actual C++ function
invocation.
I did consider that. But there is not much place for printf. This is how
it looks like:
Sisyphus (sisyph...@optusnet.com.au) writes:
If your 32-bit perl, and therefore also your binaries, use a runtime
other than msvcrt.dll (eg msvcr80.dll), then that also can cause *big*
problems - in the form of a crash. ActivePerl uses the msvcrt.dll
runtime, and that runtime won't know what
On Tue, 02 Aug 2011, Erland Sommarskog wrote:
Sisyphus (sisyph...@optusnet.com.au) writes:
Jan Dubois possibly has some ideas (and definitely has a better
understanding) about this. If he doesn't turn up here, and you wish to get
some feedback from him, try posting to the perl-win32-users
- Original Message -
From: Erland Sommarskog esq...@sommarskog.se
To: perl-xs@perl.org
Sent: Tuesday, August 02, 2011 7:55 AM
Subject: Problem with building XS module on AS 1401
I have a module Win32::SqlServer, which I distribute with binaries for
ActivePerl. With the release of
