typedef in C

What is typedef?

Some type names in C are long and repetitive — unsigned long int, struct Employee, or a tangled function-pointer type. typedef lets you give any existing type a short, readable alias, so you can use the short name everywhere instead.

Important: typedef does not create a new type. It only creates a nickname for a type that already exists. The variable behaves exactly the same — it is just easier to write and read.

A basic alias

#include <stdio.h>
typedef unsigned int uint;   // uint now means unsigned int

int main() {
    uint age = 25;
    printf("Age = %u\n", age);
    return 0;
}

Here uint is simply a friendlier name for unsigned int. Both mean the same thing to the compiler.

typedef with struct

This is the most common use. Normally you repeat the struct keyword every time; typedef removes it.

#include <stdio.h>
typedef struct {
    char name[20];
    int  age;
} Person;                 // Person is the alias

int main() {
    Person p = {"Aman", 22};
    printf("%s is %d\n", p.name, p.age);
    return 0;
}

Thanks to typedef, you write Person p; instead of struct Person p; — cleaner and closer to how other languages name types. (New to structures? See structure vs union.)

typedef for pointers and function pointers

typedef really shines when a type is hard to read. Function pointers are the classic example.

#include <stdio.h>
typedef int (*Operation)(int, int);   // alias for the messy type

int add(int a, int b) { return a + b; }

int main() {
    Operation op = add;        // clean and readable
    printf("Sum = %d\n", op(5, 6));
    return 0;
}

Without the typedef you would have to write the full int (*op)(int, int) every time. (See function pointers for the raw syntax.)

typedef vs #define

Both can name things, but they are not the same. #define is blind text replacement; typedef understands types.

Common mistakes

• Thinking typedef creates a new type — it only makes an alias.
• Using #define for pointer types and getting surprising declarations.
• Putting the alias name in the wrong place (it goes at the end of the typedef).
• Overusing typedef for simple types, which can hide what a variable really is.

Summary

• typedef gives an existing type a short, readable alias — no new type is created.
• With structs it removes the repeated struct keyword (Person p;).
• It makes pointer and function-pointer types far easier to read.
• Prefer typedef over #define for naming types — it is type-aware and safer.