Avoid to use types that are just aliases for a standard C type
See also GNOME/GLib !3003.
There is usually no reason to use the GLib-specific type names here, other than consistency. The GLib-specific one-word type names can sometimes be a little more convenient when generating a family of function names from macros. Because these types are simple aliases for a hard-coded standard C type, there should be no API or ABI issues caused by changing existing code to use the standard C names: a
char **
can already be used interchangeably withgchar **
, and name-mangling for a C++ method that takes anint
parameter is equivalent to agint
parameter.