Could the meaning of stdcall be broadened to "the standard calling
convention for libraries on the native system", i.e. pascal on Win32
(as now) and ccall on Unix? It would save a lot of fuss for interfaces
to portable libraries.
___
FFI ma
On Saturday 19 July 2003 12:51 am, Ross Paterson wrote:
> Could the meaning of stdcall be broadened to "the standard calling
> convention for libraries on the native system", i.e. pascal on Win32
> (as now) and ccall on Unix? It would save a lot of fuss for interfaces
> to p
> On Saturday 19 July 2003 12:51 am, Ross Paterson wrote:
> > Could the meaning of stdcall be broadened to "the standard calling
> > convention for libraries on the native system", i.e. pascal on Win32
> > (as now) and ccall on Unix? It would save a lot of fuss
&
On Tue, Jul 22, 2003 at 12:15:44PM +0100, Simon Marlow wrote:
> [Windows uses both __cdecl and __stdcall]
>
> So I'd say that specifying a "default" calling convention which maps to
> stdcall on Windows and ccall on Unix is probably a bad idea. You've
> j
Dnia wto 22. lipca 2003 13:52, Ross Paterson napisaĆ:
> The proposal was to have this in addition to ccall. This convention
> is currently called CALLCONV in the network, GLUT and OpenGL packages,
> with hacks to turn it into ccall or stdcall. I think it makes sense to
> regu
well, for one, you might actually want to link against some pascal
libraries on unix. and hence need stdcall. although, that would probably
require other FFI extensions anyway. Another case where it might be
useful is that it is not unheard of to link against windows DLLs on
unix. that is how
nGL packages,
> > with hacks to turn it into ccall or stdcall. I think it makes sense to
> > regularize it as stdcall.
>
> In gcc on Unix you can declare a function as "stdcall" and it will change the
> calling convention accordingly. I don't know of any library
On Tuesday 22 July 2003 3:20 pm, Ross Paterson wrote:
> OK, so the thing I want shouldn't be called stdcall, but it would be useful
> (and is already being used).
Yes to both.
Especially so if any other platform has two commonly used calling convention.
Ross Paterson <[EMAIL PROTECTED]> wrote,
> Could the meaning of stdcall be broadened to "the standard calling
> convention for libraries on the native system", i.e. pascal on Win32
> (as now) and ccall on Unix? It would save a lot of fuss for interfaces
> to port