Typedef

is a reserved keyword in the programming languages C, C++, and Objective-C. It is used to create an additional name for another data type, but does not create a new type, except in the obscure case of a qualified typedef of an array type where the typedef qualifiers are transferred to the array element type. As such, it is often used to simplify the syntax of declaring complex data structures consisting of struct and union types, although it is also commonly used to provide specific descriptive type names for integer data types of varying sizes.

Syntax

A typedef declaration follows the same syntax as declaring any other C identifier. The keyword typedef itself is a specifier which means that while it typically appears at the start of the declaration, it can also appear after the type specifiers or between two of them.
In the C standard library and in POSIX specifications, the identifier for the typedef definition is often suffixed with, such as in size_t and time_t. This is practiced in some other coding systems, although POSIX explicitly reserves this practice for POSIX data types. In modern codebases, especially in C++, this suffix is no longer popular, but does appear in some types in the C++ Standard Library along with other suffixes like.

Examples

This snippet declares the type as an alias of the type, allowing a user to use as a type in declarations where they would otherwise use :typedef int Length;
Length my_length = 3; // my_length is type 'int'

Documentation use

A typedef declaration may be used to give more contextual meaning than is given by the underlying type, hinting to the user of functions or variables a certain meaning or format is expected. For example, in the code below, the type is being further clarified to the distinct aliases and :

typedef int KmPerHour;
typedef int Points;
KmPerHour top_speed;
Points high_score;
void congratulate

The use of typedef here is used to indicate that only variables declared as should be used as the first argument, and variables declared as for the second. The value of using typedef in this manner would be for specific cases where masking the underlying type with an alias would add substantial clarity for the programmer, and not for any sort of type enforcement from the compiler, since typedefs are translated back to underlying types before any error checking occurs. For example, this code will compile, without any error:
void foo

Declaration simplification

A typedef may be used to simplify the declarations of objects having types with verbose names, such as struct, union, or enum types. The point of this is to make it more convenient to declare variables with certain types. For example,

struct NamedLocation ;
// normal declaration
struct NamedLocation location_a;
// declares NamedLocationType as an alias to the type 'struct NamedLocation'
typedef struct NamedLocation NamedLocationType;
NamedLocationType location_b; // type is 'struct NamedLocation'

Along with providing previously declared types directly after the keyword, one may also put a full definition of a struct, union, or enum. This has the effect of providing both a type definition and an alias in one statement.
typedef enum Weather WeatherType;
enum Weather yesterdays_weather;
WeatherType todays_weather;
When a definition is provided in the typedef declaration, the tag is optional, leaving only the alias. Modifying the previous snippet:
typedef enum WeatherType;
enum Weather yesterdays_weather; // ERROR: "enum Weather" does not exist.
WeatherType todays_weather; // OK
In C++, unlike in C, the tag of a,,, or type is called a class name, and can be used as a type alias automatically without any typedef declaration.
struct MyStruct ;
typedef struct MyStruct MyNewType;
struct MyStruct x; // OK in C/C++
MyNewType y; // OK in C/C++
MyStruct z; // OK in C++, error in C
The correspondence between this C++ feature and typedef is very strong, extending to the fact that it is possible to shadow the simple type name in a nested scope by declaring it as the identifier of another kind of entity. In such a case, the C-style full type name can still be used to refer to the class or enum type.
In C++, then, can be used anywhere that can be used, as long as there are no other declarations of these identifiers. The reverse is not true, however, for C++ requires the class name for some purposes, such as the names of constructor methods.
A notorious example where even C++ needs the keyword is the POSIX stat system call that uses a struct of the same name in its arguments:

int stat

Here both C as well as C++ need the keyword in the parameter definition.

Pointers

The typedef may be used to define a new pointer type.

typedef int* IntPtr;
IntPtr ptr;
// Same as:
// int* ptr;

is a new alias with the pointer type. The definition,, defines a variable with the type. So, is a pointer which can point to a variable of type.
Using typedef to define a new pointer type may sometimes lead to confusion. For example:

typedef int* IntPtr;
// Both 'cliff' and 'allen' are of type int*.
IntPtr cliff, allen;
// 'cliff2' is of type int*, but 'allen2' is of type int**.
IntPtr cliff2, *allen2;
// Same as:
// IntPtr cliff2;
// IntPtr* allen2;

Above, means defining 2 variables with type for both. This is because a type defined by typedef is a type, not an expansion. In other words,, which is the type, decorates both and. For, the type decorates the and. So, is equivalent to 2 separate definitions, and. means that is a pointer pointing to a memory with type. Shortly, has the type,.

Constant pointers

Again, because typedef defines a type, not an expansion, declarations that use the const qualifier can yield unexpected or unintuitive results. The following example declares a constant pointer to an integer type, not a pointer to a constant integer:

typedef int* IntPtr;
const IntPtr ptr = nullptr;
// This is equivalent to:
// int* const ptr = nullptr; // Constant pointer to an integer.

Since it is a constant pointer, it must be initialized in the declaration.

Structures and structure pointers

Typedefs can also simplify definitions or declarations for structure pointer types. Consider this:

struct Node ;

Using typedef, the above code can be rewritten like this:

typedef struct Node Node;
struct Node ;

In C, one can declare multiple variables of the same type in a single statement, even mixing structure with pointer or non-pointers. However, one would need to prefix an asterisk to each variable to designate it as a pointer. In the following, a programmer might assume that was indeed a, but a typographical error means that is a. This can lead to subtle syntax errors.

struct Node *startptr, *endptr, *curptr, *prevptr, errptr, *refptr;

By defining the typedef, it is assured that all variables are structure pointer types, or say, that each variable is a pointer type pointing to a structure type.

typedef struct Node* NodePtr;
NodePtr startptr, endptr, curptr, prevptr, errptr, refptr;

Function pointers

int do_math
int call_a_func)
int final_result = call_a_func;

The preceding code may be rewritten with typedef specifications:

typedef int ;
int do_math
int call_a_func
int final_result = call_a_func;

Here, is the new alias for the type. A is a pointer to a function that returns an integer and takes as arguments a float followed by an integer.
When a function returns a function pointer, it can be even more confusing without typedef. The following is the function prototype of signal from FreeBSD:

void ));

The function declaration above is cryptic as it does not clearly show what the function accepts as arguments, or the type that it returns. A novice programmer may even assume that the function accepts a single as its argument and returns nothing, but in reality it also needs a function pointer and returns another function pointer. It can be written more cleanly:

typedef void ;
sighandler_t signal;

Arrays

A typedef can also be used to simplify the definition of array types. For example,

typedef char ArrType;
ArrType arr = ;
ArrType* pArr;
// Same as:
// char arr = ;
// char ;

Here, is the new alias for the type, which is an array type with 6 elements. For, is a pointer pointing to the memory of the type.

Type casts

A typedef is created using type definition syntax but can be used as if it were created using type cast syntax. For instance, in each line after the first line of:

// `FuncPtr` is a pointer to a function which takes a `double` and returns an `int`.
typedef int ;
// Valid in both C and C++.
FuncPtr x = nullptr;
// Only valid in C++.
FuncPtr y = FuncPtr;
FuncPtr z = static_cast;

is used on the left-hand side to declare a variable and is used on the right-hand side to cast a value. Thus, the typedef can be used by programmers who do not wish to figure out how to convert definition syntax to type cast syntax.
Without the typedef, it is generally not possible to use definition syntax and cast syntax interchangeably. For example:

void* p = nullptr;
// This is legal.
int = ) p;
// Left-hand side is not legal.
int y = ) p;
// Right-hand side is not legal.
int = );

Usage in C++

In C++ type names can be complex especially with namespace clutter, and typedef provides a mechanism to assign a simple name to the type.

std::vector> values;
for ; i != values.end; ++i)

and

typedef std::pair Value;
typedef std::vector Values;
Values values;
for ; i != values.end; ++i)

C++11 introduced the possibility to express typedefs with instead of. For example, the above two typedefs could equivalently be written as

using Value = std::pair;
using Values = std::vector;

Use with templates

C++03 does not provide templated typedefs. For instance, to have represent for every type one cannot use:

template
typedef std::pair StringPair; // Doesn't work

However, if one is willing to accept in lieu of, then it is possible to achieve the desired result via a typedef within an otherwise unused templated class or struct:

template
class StringPair ;
// Declare a variable of type std::pair.
StringPair::Type myPairOfStringAndInt;

In C++11, templated typedefs are added with the following syntax, which requires the keyword rather than the keyword.

template
using StringPair = std::pair;
// Declare a variable of type std::pair.
StringPair myPairOfStringAndInt;

Other languages

In SystemVerilog, typedef behaves exactly the way it does in C and C++.
In many statically typed functional languages, like Haskell, Miranda, OCaml, etc., one can define type synonyms, which are the same as typedefs in C. An example in Haskell:

type PairOfInts =

This example has defined a type synonym as an integer type.
In Swift, one uses the keyword to create a typedef:

typealias PairOfInts =

C# contains a feature which is similar to the typedef or the syntax of C++.

using InteropMarshal = global::System.Runtime.Interop.Marshal;
using MyEnumType = Wikipedia.Examples.Enums.MyEnumType;
using StringListMap = System.Collections.Generic.Dictionary>;

In D the keyword allows to create type or partial type synonyms.

struct Foo
alias FooInt = Foo!int;
alias Fun = int delegate;

In Python, a type can be aliased using the import as statement:

from re import Pattern as RegexPattern

can now refer to re.Pattern as RegexPattern

In Rust, a type can be aliased using the use as statement:

// math.rs
pub fn add -> i32
pub fn subtract -> i32
// main.rs
mod math;
// rename add to sum, subtract to diff
use math::;
fn main

Usage concerns

Kernighan and Ritchie stated two reasons for using a typedef. First, it provides a means to make a program more portable or easier to maintain. Instead of having to change a type in every appearance throughout the program's source files, only a single typedef statement needs to be changed. size_t and ptrdiff_t in are such typedef names. Second, a typedef can make a complex definition or declaration easier to understand.
Some programmers are opposed to the extensive use of typedefs. Most arguments center on the idea that typedefs simply hide the actual data type of a variable. For example, Greg Kroah-Hartman, a Linux kernel hacker and documenter, discourages their use for anything except function prototype declarations. He argues that this practice not only unnecessarily obfuscates code, it can also cause programmers to accidentally misuse large structures thinking them to be simple types.