Dear,
On the wiki Fortran API much C link, whether this will affect the performance of data calls?
Have a Fortran directly calling the KDB+ way?
Thanks,
Yuanfei
Dear,
On the wiki Fortran API much C link, whether this will affect the performance of data calls?
Have a Fortran directly calling the KDB+ way?
Thanks,
Yuanfei
Hi Yuanfei,
Kx don’t provide a native interface to Fortran. External interfaces to kdb+ come in two forms - either they can use the kdb+ IPC interface, mimicking another kdb+
process talking over a socket (examples are the Java and C# interfaces), or q can be extended by calling C functions directly by linking to them in a shared library.
The underlying architecture of kdb+ is based on C, and the C interface allows K data structures to be created and accessed directly without any translation step,
so performance shouldn’t suffer. The following doc (which you may already have found) gives details and examples on how to call Fortran via dynamically linked C functions:
http://code.kx.com/wsvn/code/contrib/jludlow/docs/fortran.pdf?format=raw
Mark Rooney
Financial Software Developer
AQUAQ Analytics
? 2015?1?13??? UTC+8??6:43:52?mark…@aquaq.co.uk???
Hi Yuanfei,
Kx don’t provide a native interface to Fortran. External interfaces to kdb+ come in two forms - either they can use the kdb+ IPC interface, mimicking another kdb+
process talking over a socket (examples are the Java and C# interfaces), or q can be extended by calling C functions directly by linking to them in a shared library.
The underlying architecture of kdb+ is based on C, and the C interface allows K data structures to be created and accessed directly without any translation step,
so performance shouldn’t suffer. The following doc (which you may already have found) gives details and examples on how to call Fortran via dynamically linked C functions:http://code.kx.com/wsvn/code/contrib/jludlow/docs/fortran.pdf?format=raw
Thanks
Mark Rooney
Financial Software Developer
AQUAQ Analytics