From: rfnum AT www DOT twinux DOT com
Subject: re: stdcall
6 Jan 1999 22:53:29 -0800
Message-ID: <Pine.LNX.4.04.9901061834060.22723-100000.cygnus.gnu-win32@www.twinux.com>
References: <Pine DOT SUN DOT 3 DOT 93 DOT 990105170906 DOT 4531C-100000 AT modi DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Mumit Khan <khan AT xraylith DOT wisc DOT edu>
Cc: gnu-win32 AT cygnus DOT com

On Tue, 5 Jan 1999, Mumit Khan wrote:

> > When writing a win32 application, how are STDCALL functions handled?
> > If the windows API expects to pop arguments to a call, how does 
> > egcs handle it?  Does it do the 'right' thing?  Is there an interface
> > layer that does it?  Is this option available available on other
> > platforms?
> 
> They're handled exactly as the GCC documentation suggests. Yes, it 
> mostly does the right thing[1]. I'm not sure what you mean by an 
> interface layer, but see [2] below. And, yes, it's supported under 
> all platforms; why you'd want to use it on any other platform where 
> you don't have to is of course an altogether different issue!

Because I'm working on the inverse problem.  I am making an implementation
of the windows api's for unix.  So when gnu-win32 is used to write
window applications, those same binaries, on say intel linux, could
run unchanged.  I can do this now, for small win32 applications, 
and have a layer to 'do the right thing' for non-gcc intel platforms.
This feature means I won't need that layer. Thanks.

robf

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".