Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Why I use gcc Date: Tue, 27 Sep 2016 08:52:29 -0700 Organization: None to speak of Lines: 29 Message-ID: References: <591c35dc-315d-4293-bf36-53ffa8eb044d@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="23050"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18AH4Wa8uC8efQn8mGpfIq6" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:llru9+ohj7ChsbP0viESjcgDfBI= sha1:ayc1gZ9yjRGnssEtY/4erdl4Pco= Xref: csiph.com comp.lang.c:94152 jacobnavia writes: [...] > The _cdecl calling convention doesn't exist, of course. It is just plain > C DECLarations, i.e. normal C. [...] You say it doesn't exist, then you explain what it is? BTW it's "__cdecl", not "_cdecl" (though I wouldn't be surprised if both forms are accepted). https://msdn.microsoft.com/en-us/library/zkwh89ks.aspx __cdecl Visual Studio 2015 Microsoft Specific __cdecl is the default calling convention for C and C++ programs. Because the stack is cleaned up by the caller, it can do vararg functions. The __cdecl calling convention creates larger executables than __stdcall, because it requires each function call to include stack cleanup code. The following list shows the implementation of this calling convention. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"