women()
{
goto bathroom;
bathroom:
while (1) ;
}

To be completely reserved an identifier must start with an underscore and having an uppercase letter or an other underscore as second character.
If the identifier only starts with an underscore it is reserved only in the ordinary and tag name space. Standard 7.1.3 .
As strange it might seem, in C (not C++) using the label _hello: or using the identifier a__b is legit.

Unsing typedef struct c c; works also in C++, but it unneeded.

Anyway, you are right about the main point, in a standard compliant C compiler the tag and ordinary name space are separate, no need to invent a new name. Old compilers get confused, but newer should not anymore (surely it does not gcc 4.3.3)

The correct struct definition would be:

typedef struct Woman Woman;
struct Woman
{
int age;

/* TODO: implement these functions. */
void (*complain) (Woman *);
void (*cook) (Woman *);
void (*clean) (Woman *);
/* These functions should be enough. */
};

typedef struct Foo { … } Foo;

The typedef can have the same name as the structure tag itself, no need for the extra underscore. In fact, identifiers beginning with an underscore are reserved for use by the system headers and such, so should not be used for this.

Using the same name for both parts might break in C++ though, I’m not sure.