The following is the function of VC definition:
Int32 DAQmxReadAnalogF64 (TaskHandle TaskHandle, int32 numSampsPerChan, float64 timeout, bool32 fillMode, float64 readArray [], uInt32 arraySizeInSamps, int32 * sampsPerChanRead, bool32 * reserved);

When converted to Delphi:
The function DAQmxReadAnalogF64 (taskHandle: Longint;
NumSampsPerChan: Longint;
Timeout: Double;
FillMode: DAQmxFillMode;
ReadArray: PDouble;
ArraySizeInSamps: Longint;
SampsPerChanRead: PLongint;
Reserved: PChar) : Longint; Stdcall;

Program calls or complains, the warrior is a data type definition with VC right?

CodePudding user response:

Note that each entry type and calling conventions, the default is c cdecl rather than stdcall

CodePudding user response:

10, 89 is a data definition is wrong

CodePudding user response:

Should be to call this function when readArray: PDouble; This parameter is not defined, but does not know how to define the pointer and use,

CodePudding user response:

The Jefferson memorial. JPG

CodePudding user response:

[img] http://www.nbu.cc/viewfile/1186/DLaZuVi2/[/img]

CodePudding user response:

UInt32==& gt; Cardinal.
Bool32==& gt; Longint or Cardinal