Re: Style convention question

[Sven Neumann <sven gimp org>]

Hi,

Derek Simkowiak <dereks realloc net> writes:

> 	Why does Glib do this:
> 
> typedef struct _GFoo GFoo;
> struct _GFoo {
> 	/* [...] */
> };
> 
> 	...instead of the more compact
> 
> typedef struct {
> 	/* [...] */
> } GFoo;

this allows you to put the typedef into a different place than the 
structure declaration. For apps it makes sense to put all typedefs
into one header that is included by all C files so the types are 
known everywhere, while only a few C files need access to the structs
members and need to include the respective header file. Often it is
also desirable to make the structure declaration private by moving
it into the C file. The rest of the app then can use the type, but
needs to access it thru provided accessor functions. GLib/GTK+ does 
not make heavy use of this possibilities, but IMO it's a good habit 
to stick with that style for all typedefs.


Salut, Sven