PureBasic Forums - English

Hi All,

I need to import a .lib file that return float numbers.

For example : I must chen use the function this way :
MyFloat.f = RotateObject( ObjectID.l, FX.f, FY.f, FZ.f )

The problem is that I don't get MyFloat correctly as floating number.

I must do that to get things works :
MyInteger.l = RotateObject( ObjectID.l, FX.f, FY.f, FZ.f )
MyFloat.f = PeekF( @MyInteger )

Is it a PureBASIC import BUG or Am I doint something wrong ?

I've already tried this
It doesn't work.
It gives the same result than when I don't add the .f at the end of function name.

How it gets returned depends on your compiler that you used to create the .lib. You should create a test application in the same language, check the ASM output from it and see how the test application gets the returned value.

I don't know if PB supports anything other than returning values in EAX (on Windows/x86), so if it gets returned somewhere else, such as the top of the FPU stack, then you'll need to write a small assembly language procedure to call the function for you.

The .lib to import was developed using Microsoft Visual C++ ..
From the author, it directly send back simple precision floating number.

@tinman, PB takes its floating point returns from the top of the fpu stack - both for internal functions and imported ones.

@Freddix : the fact that you get the same return when importing the function with .f as without suggests that you are perhaps mis-using this function somehow!

**EDIT : just seen the

I must do that to get things works :
MyInteger.l = RotateObject( ObjectID.l, FX.f, FY.f, FZ.f )
MyFloat.f = PeekF( @MyInteger )

All this means is that the function is returning the float value in eax rather than leaving it at the top of the floating point stack - which is fair enough I guess (if a little strange!)

@srod :
In fact, I don't exactly get the same result. I don't get the same number but both number are recognized as integer (.l) by PureBASIC ... and never change ... apparently, I always get the pointer to the float and not the float itself... I'll check with the author of the plugin concerning this.

Thank you.

Regards,
Fred
Odyssey-Creators

Sorry I don't understand. Is this code :
giving you the correct result?

If so then there is no pointer being returned, simply that the result is being placed in eax. Returning a pointer would require that the function reserved some memory to hold the float value and it is very unlikely that any public function is going to do that because there would be the problem of freeing that memory!

Just for info, I've tested with MSVC 2005 and it returns single precision floats in the FPU stack. Using .f in the import worked fine with the PB code I tested.

Yes my understanding is that VC, with all supported calling conventions, will return floats from functions by simply leaving them on the top of the fpu stack. This code of Freddix's must be taking steps to leave the result in eax for some reason as yet unknown?

@Srod : You're probably right.
I'm not the author of the .lib files I'm working to integrate in PureBASIC ... but with: it working fine.
As I've done a small program to get the functions names an create the Import file, I've modified it to create WRAP Procedure for .lib functions that'll return a .f in eax format ...

Now all is correctly working...

In fact, I can reveal what these .lib files are ... They're DarkSDK From TheGameCreators.
I've found the way to make DarkSDK become compatible with PureBASIC and it's top :p

I'm working now on translating DarkSDK C++ source code samples to PureBASIC source code samples
I've checked with my contact(s) at TheGameCreators and we will check how it will be released ....

I think DarkBasic uses CDECL, so you have to ImportC and not Import

@ts-soft : It's already what I do

freddix wrote:@ts-soft : It's already what I do

The info of darkbasic comes to late