Naming scheme for typedefs

Question

I\'m working on a library that extensively used constructs like

typedef struct foo_bar_s {
    ...
} foo_bar_t;

It\'s a bad idea to use the

Answer 1

I use the naming conventions used in Dave Hanson's C Interfaces and Implementations: a type is named with the module name and a capital T. So for example, the type of sequences is Seq_T, and the type of hash tables is Table_T. Within the implementation of a module Hanson uses #define to abbreviate just to T. This is basically Modula-3 conventions applied to C programming, but I find that after a brief initial shock it works well.