> One common idiom is to use a typedef while defining the type.  In this case,
> you might write:
> typedef struct object object_t;
> typedef object_t *(*method_t)(object_t *receiver, ...);
>
> Okay, so in the initial example, why the typedef? What function is it
> performing here? I thought typedef was used to alias types, and yet here it
> doesn't seem to be doing anything... if method_t is a function pointer, why
> does there need to be a typedef in front of it?

method_t is the name of the type alias that the typedef defines.
function pointers have a funky syntax ordering.  Have a look at this:

http://www.newty.de/fpt/index.html

wes

_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc

Reply via email to