From mboxrd@z Thu Jan 1 00:00:00 1970 From: J Russell Smyth To: "'GNU-Win32'" Subject: yes, why @NN?!(was :Re: .def files for stdcall functions ) Date: Fri, 12 Sep 1997 22:41:00 -0000 Message-id: <34198046.9789F5D2@voicenet.com> References: <01BCBF89.A3905060@gbird0> X-SW-Source: 1997-09/msg00249.html 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. I too have wondered about this .. as I have been attempting to create dll's that can be used with other languages, mainly Visual Basic, I have found this frustrating and annoying! to create a dll for use with VB and gcc, I must create all functions with the @NN and alias all of them to non-@NN names for VB! One quickview of ANY M$ dll shows that microsofts dll's do not contain this info, where cygwin does, causing great grief for other-language-programmers. This problem is also encountered with LCC which I use extensively... Russ Smyth jrussell@voicenet.com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".