[DiscordArchive] <@283455627538333696> what for? I can use Cython with native types?
[DiscordArchive] <@283455627538333696> what for? I can use Cython with native types?
Original source
<@283455627538333696> what for? I can use Cython with native types?
rektbyfaith
10-13-2018, 12:04 PM #1Archived author: Skarn • Posted: 2018-10-13T12:04:36.658000+00:00
Original source
<@283455627538333696> what for? I can use Cython with native types?
Original source
To reiterate what others said: WINAPI indicates that it uses the default Windows API calling convention so that the DLL will export the function in a standard format. See CascPort.h for what it's defined as (if anything) for other platforms. And a HANDLE is just an opaque identifier for some object, and the actual meaning is completely implementation specific.
rektbyfaith
10-13-2018, 12:05 PM #2Archived author: Quantam • Posted: 2018-10-13T12:05:22.144000+00:00
Original source
To reiterate what others said: WINAPI indicates that it uses the default Windows API calling convention so that the DLL will export the function in a standard format. See CascPort.h for what it's defined as (if anything) for other platforms. And a HANDLE is just an opaque identifier for some object, and the actual meaning is completely implementation specific.
Original source
A true HANDLE with Windows kernel functions is an index into the handle ("file descriptor") table. Other libraries may have them be pointers to internal data structures or whatever. More recently Windows has devised the concept of encoding pointers in a boot-time-specific way to prevent stack overflow attacks that access pointer HANDLES.
rektbyfaith
10-13-2018, 12:07 PM #3Archived author: Quantam • Posted: 2018-10-13T12:07:43.840000+00:00
Original source
A true HANDLE with Windows kernel functions is an index into the handle ("file descriptor") table. Other libraries may have them be pointers to internal data structures or whatever. More recently Windows has devised the concept of encoding pointers in a boot-time-specific way to prevent stack overflow attacks that access pointer HANDLES.
Original source
Okay yeah, Cython works too
rektbyfaith
10-13-2018, 12:08 PM #4Archived author: Quantam • Posted: 2018-10-13T12:08:15.636000+00:00
Original source
Okay yeah, Cython works too
Original source
See CascPort.h
rektbyfaith
10-13-2018, 12:08 PM #5Archived author: Quantam • Posted: 2018-10-13T12:08:20.091000+00:00
Original source
See CascPort.h
Original source
Either treat HANDLE as an intptr_t or a void *
rektbyfaith
10-13-2018, 12:08 PM #6Archived author: Quantam • Posted: 2018-10-13T12:08:54.145000+00:00
Original source
Either treat HANDLE as an intptr_t or a void *
Original source
Oh right. HANDLES by definition are pointer-sized on Windows
rektbyfaith
10-13-2018, 12:09 PM #7Archived author: Quantam • Posted: 2018-10-13T12:09:20.650000+00:00
Original source
Oh right. HANDLES by definition are pointer-sized on Windows
Original source
okay
rektbyfaith
10-13-2018, 12:09 PM #8Archived author: Skarn • Posted: 2018-10-13T12:09:50.495000+00:00
Original source
okay
Original source
I'm thinking on x64 WINAPI == __cdecl, but I'm not certain about that. It's __stdcall == Pascal convention on x86
rektbyfaith
10-13-2018, 12:10 PM #9Archived author: Quantam • Posted: 2018-10-13T12:10:22.608000+00:00
Original source
I'm thinking on x64 WINAPI == __cdecl, but I'm not certain about that. It's __stdcall == Pascal convention on x86
Original source
let me see if that works
rektbyfaith
10-13-2018, 12:10 PM #10Archived author: Skarn • Posted: 2018-10-13T12:10:47.711000+00:00
Original source
let me see if that works
1 Guest(s)
1 Guest(s)