From: Scott Christley <scottc@net-community.com>
To: Colin Peters <colin@bird.fu.is.saga-u.ac.jp>
Cc: "'GNU-Win32'" <gnu-win32@cygnus.com>
Subject: RE: .def files for stdcall functions (was: linking problems with the minimalist version)
Date: Fri, 12 Sep 1997 06:55:00 -0000 [thread overview]
Message-ID: <199709121413.HAA19519@duncan.net-community.com> (raw)
At 02:39 PM 9/12/97 +0900, Colin Peters wrote:
>
>My beef with all this is: why does GCC do it this way at all? What purpose
>does the @NN serve? After all, GCC knows how to generate the correct
>function call given a prototype, it *generates* the @NN, so it doesn't
>need it to know what to do. I don't think any other compilers add on @NN
>to the names of WINAPI functions like this. Why doesn't GCC just use the
>plain function name and call it with PASCAL calling convention? Someone
>please enlighten me.
It's a Microsoft thing not GCC; if you look at the Microsoft libraries you
will see that they have the @NN tacked onto the function names. Special
code had to be added to GCC so that it produced the appropriate functions.
That is why you see these predefinitions when you run GCC with the -v flag
-D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__))
Now why Microsoft felt it was necessary to tack on @NN, I don't know.
Scott
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-09-12 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-12 6:55 Scott Christley [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-17 0:03 Colin Peters
1997-09-17 5:07 ` Mikey
1997-09-11 23:07 Colin Peters
1997-09-12 4:40 ` Gunther Ebert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199709121413.HAA19519@duncan.net-community.com \
--to=scottc@net-community.com \
--cc=colin@bird.fu.is.saga-u.ac.jp \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).