Demystifying C Programming Calling Conventions


Calling conventions in C programming play a vital role in defining how functions communicate with each other and how parameters and return values are handled. It is essential for developers to understand different calling conventions to ensure efficient and correct program execution. In this article, we will explore cdecl, Pascal, callbacks, and the WinAPI calling convention in the context of C programming, shedding light on their significance and practical implementation.

cdecl Calling Convention:

The cdecl (C declaration) calling convention is widely used as the default calling convention in C programming. It provides a flexible and straightforward mechanism for function calls.

void __cdecl CMyMethod() { return; }

Parameter Passing: Function arguments are pushed onto the stack from right to left. The caller function is responsible for cleaning up the stack after the function call.

Return Value: The return value is usually stored in the EAX register (on x86 platforms) or the appropriate register based on the platform's calling convention.

Pascal Calling Convention:

The Pascal calling convention differs from the cdecl convention and is commonly used in languages like Pascal and Delphi.

void __stdcall CMyMethod() { return; }

Parameter Passing: Function arguments are pushed onto the stack from left to right. The called function cleans up the stack after returning.

Return Value: The return value is typically stored in a predefined location, such as a register or a specified memory location.

Callbacks in C:

Callbacks are essential for enabling communication and interaction between different parts of a program or between different programming languages. Implementing callbacks in C requires attention to calling conventions.


Pascal Callbacks in C: When incorporating Pascal callbacks in C programs, it is essential to align the calling conventions of both languages. To achieve this, the cdecl calling convention is commonly used in the C function that receives the Pascal callback. This ensures compatibility in terms of stack manipulation and cleanup, allowing seamless communication between the two languages.

WinAPI Calling Convention:

The WinAPI calling convention, often referred to as stdcall, is specific to the Windows platform and is widely used for Windows API functions.

void __stdcall CMyMethod() { return; }

Parameter Passing: Function arguments are pushed onto the stack from right to left, similar to the cdecl convention.

Return Value: The called function is responsible for cleaning up the stack before returning, ensuring proper stack alignment.

Compatibility: When working with the WinAPI, it is crucial to adhere to the stdcall calling convention to ensure compatibility with Windows systems and maintain proper stack management.

Practical Implementation and Best Practices:

To make the most of calling conventions in C programming, consider the following best practices:

Understand Platform-Specific Conventions: Different platforms and architectures may have their own unique calling conventions. Familiarize yourself with the conventions used in your target environment to ensure compatibility and optimal performance.

Documentation and Consistency: Maintain clear documentation about the calling conventions used in your codebase. Consistency in adhering to the chosen conventions will help avoid confusion and improve code readability.

Handle Callbacks Carefully: When working with callbacks, be mindful of the calling conventions of the involved languages. Use compatible conventions and ensure proper alignment for seamless integration.

Leverage Platform-Specific APIs: When working with platform-specific libraries, such as the WinAPI, adhere to the prescribed calling convention for optimal compatibility and functionality.


Understanding calling conventions is essential for mastering C programming and ensuring efficient and reliable code execution. In this article, we explored the cdecl calling convention as the default in C, the Pascal calling convention, the integration of Pascal callbacks in C programs using cdecl, and the WinAPI calling convention (stdcall). By following best practices and considering platform-specific conventions, developers can write robust and interoperable C code, enabling seamless communication between functions, languages, and APIs.

About our authors: Team EQA

Further readings

Where is WinMain() function in MFC application ?

MFC hides WinMain in its framework and includes source file on WinMain(). This explains how framework calls global CWinApp::Initinstance() from entry WinMain.

What is the utility of CWinApp class?

This is constructed during global C++ objects are constructed and is already available when Windows calls the WinMain function, which is supplied by the ...

Basic steps in Win32 GUI Application with source code.

Define a custom Window class structure, Register the class name, CreateWindow, Show windows and write message get and dispatch loop statements. Define the Window CallBack procedure and write the handlers.

What is a Window CallBack procedure and what is its utility?

DispatchMessage() is a API which indirectly triggers the Window CallBack procedure. Message structure members from this function are passed to the CallBack procedure. CallBack procedure should implement event handlers depending on the need of the application.

What are LPARAM and WPARAM in window proc function?

LPARAM and WPARAM are the two parameters in Window CallBack procedure. They signifies parameters of various events. They are used in handing individual events.

What are the basic steps of a typical MFC based application?

We need to write WinMain and need to follow all these in a Win32 application. However we need not to write much if we are writing an application with MFC ...

Learn on Youtube