Thread: Typedef advantages?

Use typedef to give a long and difficult type an alias.

Code:

typedef std::map< int, vector<string> > StrIntMap;
typedef int(*compare)(void *a, void *b) CompFn;

It is better to assume that there is no advantage at all, and only use typedef if writing out a variable's type is very fugly looking or especially error prone.

Use it when you gain a lot more in terms of clarity than you lose with the loss of detail in the code.

Function pointers are notoriously hard to get right, and exceedingly verbose if you have several parameters. This is usually a good idea to typedef these.

For a given T, using a typedef for T*
Eg. typedef int *intp;
You haven't saved any typing, you may as well type a * before something as type a 'p' after it. But you have made the code a hell of a lot harder to trace through since the number of *'s you use on the usage no longer agrees with the number of *'s on the declaration.
This is a bad use of typedef.

If you write any class which you want to be usable like an STL container, you'll need to typedef things like iterators and the like.

Also, citizen, I think your function pointer typedef should just be:

Code:

typedef int(*CompFn)(void *a, void *b);