Is anyone actually specifying stdcall ccall calling conventions in a foreign import? I want to pull it out of GHC but I don't want to break anything. Simon
Is anyone actually specifying
stdcall ccall
calling conventions in a foreign import?
hslibs/win32/Win32Dialogue.gc uses stdcall. cvs annotate says that this was written by Sigbjorn in October 1999. I'm not sure whether anyone depends on this. (The HGL definitely does not because it doesn't use dialogue boxes.) I imagine there will also be a lot of stdcall stuff in HDirect generated wrappers for COM components. Alastair ps I think "stdcall" is also known as "pascal". Don't know if that helps the story on viewing C as two languages though - you're going to have a hard time persuading people to view COM methods as though they were written in Pascal :-)
Hi all. Sorry to butt in as an interloper who hasn't followed the entire strand of discussion.
Is anyone actually specifying
stdcall ccall
calling conventions in a foreign import?
hslibs/win32/Win32Dialogue.gc uses stdcall.
....
I imagine there will also be a lot of stdcall stuff in HDirect generated wrappers for COM components.
....
ps I think "stdcall" is also known as "pascal". Don't know if that helps the story on viewing C as two languages though - you're going to have a hard time persuading people to view COM methods as though they were written in Pascal :-)
In case you aren't aware of this, Windows DLL's by default, (actually always, as far as I know) use the stdcall (Pascal) calling convention. I personally hope that you won't drop anything which facilitates using Haskell under Windows. Cheers Mike Thomas.
participants (3)
-
Alastair Reid -
Mike Thomas -
Simon Peyton-Jones