User Tools

Site Tools


vo_to_net:pcall

This is an old revision of the document!


PCall vs PCallNative

In the first Vulcan versions, PCall was not supported anymore, so this code would not have worked:

PCall( ptrFunction, @strWinOsVersionInfo )

There was only a function PCallNative to use (knowing the return type):

PCallNative<int>( ptrFunction, @strWinOsVersionInfo )

Using the Vulcan runtime, it was preferred to use PCallNative, but in the X# runtime the development team used another approach, so they recommend to use again PCall.

The following was stated by a member of the development team:

A delegate is created by the compiler and the parameters for the delegate have to be determined by the compiler . In the case of PCallNative it looks at the actual arguments to “guess” the types. The return type is then the type as specified in the code. In the case of PCall it copies both the parameter types and return value of the function in the declaration to the delegate. The compiler then emits the code to use the native function pointer and call this with the managed delegate. For this reason I would recommend using PCall because the function name used in the declaration gives you full control of the parameter types in the delegate.

Please see major details in the X# Forum discussion: www.xsharp.info/forum/public-product/752-voxporter-icon-naming-problem

vo_to_net/pcall.1531067056.txt.gz · Last modified: 2018/07/08 16:24 by wolfgangriedmann