Subj : Re: __turboFloat problem To : borland.public.cpp.borlandcpp From : "Martin Schneider" Date : Wed Sep 10 2003 06:58 pm > > bcc32 -c -tWM -DMSC_CORE_BC_EXT example.c > > This is C code so you do not want runtime type id or exception handling. > Consider adding the options -RT- -x- I think I want exception handling, as these exceptions are being forwarded to the Python language which displays the error. > Do the two machines have different compiler versions? No, not at all. Freshly downloaded package installed on both machines. > Could one of the machines not have a compiler patch or update installed that > the other one has installed? If I recall correctly the patches also updated > the libraries. I didn't even knew there are patches. Here comes the weird thing: I downloaded the patch and, just to be sure, wanted to reproduce the error _before_ installing it. Compiled, and -voila- no error! ????!? What a reboot after installation can do... I am getting sick with this :-) > I do not know the effect of defining the macro MSC_CORE_BC_EXT. Neither do I - I just copied the option from the tutorial I found which said it is essential to make it work. > Go to the command line and select the compiler's LIB directory. Give this > command > > tlib /C cw32mt.lib , cw32mt.lst > > Pull the cw32mt.lst file up in an editor and confirm if there is a public > symbol named __turboFloat in that library. I found: initcvt size = 32 __floatconvert __turboFloat I did the same thing to the mti version: xinitcvt size = 4 __turboFloat > Remember that dynamic linked means the RTL DLL's must be on the > machine and, if the exe or dll frees something the other allocated, then > memmgr.lib must be linked BEFORE all but noeh32.lib for both so that the exe > and dll share the same memory manager even if static linked. Sh*t :-) Now I know why I like VisualBasic. Just click and it runs :-) Thanks anyway for your extensive help. Martin .