CallFunction with PB4.40

[Karbon]

I don't know if this is a bug but it's certainly something that worked before 4.40

---------------------------
PureBasic
---------------------------
Line 6701: Bad parameter type, number expected instead of string.
---------------------------
OK
---------------------------

That's from a CallCFunction() call.

I see this in the changelog : " Changed: Call(C)Function(Fast) parameters have been changed from 'Any' to 'Integer'."\

What does that mean exactly? The documentation is exactly the same as far as I can tell. The function(s) I'm calling needs a string parameter passed in.

[ts-soft]

use @mystring.s or @"bla"
or better, don't use callfunction, use prototypes

[Karbon]

I try not to fix things that aren't (or weren't) broken

Guess I'll be switching. Kind of wish this was documented!

[SFSxOI]

Did you try pointers with it?

[Karbon]

Pointers it was!

[blueznl]

Many of us posted this as a bug or a question, myself included It was in the list of changes IIRC though...

[ts-soft]

use @mystring.s or @"bla"

this a pointers with the @, i think my english is to bad

[Marco2007]

use @mystring.s or @"bla"
or better, don't use callfunction, use prototypes

Thomas, I use the @-thing....why is better to use prototypes? Any problems with the @-thing?

[Seldon]

OK, but couldn't our PB compiler make it for us ? I mean when we pass a string to a DLL, it passes the pointer instead (like it has been so far). It's BASIC after all. Maybe, are there any other problems ?

[moogle]

why is better to use prototypes?

Because I think then you can call the function name directly in your code once you set up the prototype correctly, instead of CallFunctionFast() etc, etc.