...-1.35-uQ0fnc/blib/lib:/usr/local/src/CPAN/build/XML-LibXML-1.66-dso32B/blib/arch:/usr/local/src/CPAN/build/XML-LibXML-1.66-dso32B/blib/lib:/usr/local/src/CPAN/build/Test-Differences-0.4801-yzt! Vc6/blib /arch:/usr/local/src/CPAN/build/Test-Differences-0.4801-yztVc6/blib/lib:/usr/local/src/CPAN/build/Test-Warn-0.11-Ptv0sU/blib/arch:/usr/local/src/CPAN/build/Test-Warn-0.11-Ptv0sU/blib/lib:/usr/...

... version does not support it, so it might have nothing to do with the test failing. You said it. D4029 simply means that it's impossible for the compilation to be optimized by the standard use. I am not sure how to progress this, any suggestions? I'm not sure, either. Maybe my Perl is ActivePerl Build 817, which is built by VC6, whereas I use VC7. Regards, Taro Nishino

... INFINITE is not defined, the code won't compile. The only thing I can think of is that $! isn't getting set properly, but I don't know how that could happen. It appears your perl.exe was built with VC6, and you're now using VC7, but I have a report that that works. Could you try this patch? We could at least find out what $! is set to. --- lib/Win32/IPC.pm (revision 276) +++ lib/...

...*2yO_-SoXg_32*5fdre(I_rvC+/JE!yw?y47p\ajJIep<nN(ZGwu+vpB@A1yGotYVH7:\LCwm!%%b`WuG%%=?-JBngivaGD?9$WY,R/M`U<EIfOyPRH:vI1GWK8v9.AaX8wh$VlU^Y%%P(Ib:/)!-&$m\El,#yKkQ>hr6MiW!huyKiDBLYBFQ]yL/F8XopR4"VC6)of5&]V;P3P+:90#8Kp'DQ'ue>!i$ghuF%%p._^:$Qa5rU0vTAsEQK8uiXo;<;BXLaUV7Y.G27'jK0T0N#. ,XmF)0#eEcGG@OWnMHow0WY[X2l`[MT!EaaI%%H0%%BY(mS.AJ4QlqrlAs9SvDgFJj<K10?dtnm&:JJoib`try7)BH0;OlvB`6/(=9

My environment is: OS: Windows XP,VC6(sp4),db-4.5.20 The sample code is { Db *pDb=new Db(NULL,0); delete pDb; //Here will catch one heap error. } I don't konw I use it in wrong way or I need compile file with special macro definition.

nsdevelop12@yahoo.com writes: I have a bunch of Fortran files containing subroutines, which I've compiled into a .DLL using Visual Fortran 6. I want to call them from other C++ programs (Windows, VC6), but in order to do that I have to manually create header files such as: extern "C" { void __stdcall FORTRAN_SUBROUTINE( const char* name, int name_size, const int* ...

..., 20 Dec 2007 13:57:43 +0100, RobertFiegender wrote: Remark: The PlayDMO example from DX9 SDK doesn't show property pages of DMOs under Vista, either. No matter if compiled with VC6 or VS2005. Does anyone has got a hint for me? See if registering proppage.dll works ("regsvr32 proppage.dll" from the location of the file). You'll find it located in the SDK bin ...

...Thu, 20 Dec 2007 13:57:43 +0100, RobertFiegender wrote: Remark: The PlayDMO example from DX9 SDK doesn't show property pages of DMOs under Vista, either. No matter if compiled with VC6 or VS2005. Does anyone has got a hint for me? See if registering proppage.dll works ("regsvr32 proppage.dll" from the location of the file). You'll find it located in the SDK bin directory so...

Remark: The PlayDMO example from DX9 SDK doesn't show property pages of DMOs under Vista, either. No matter if compiled with VC6 or VS2005. Does anyone has got a hint for me? Thanks, Robert

Stefan Reuther <stefan.news@arcor.de> wrote: Der Debugger von VC6 ist immerhin ganz nützlich, um den EIP ein paar Instruktionen weiterzusetzen, wenn Excel mit einem Segfault absemmelt. Dann kann man wenigstens noch speichern. Das passiert bei mir nämlich immer dann, wenn ich die CD-Schublade anfasse. Schuß in Bluescreen: InCD deinstallieren. -- Never be afraid to try something ...