gperf suggestions

[Reuben Thomas]

A couple of requests for the next version of gperf (I'm using 2.7.2; sorry
if I'm out of date):

1. Can you use an ISO standard test to find out whether an ISO C99 compiler
is being used, and if so use the inline keyword, so that inlining isn't only
available on gcc and C++ compilers?

2. In wordlist, can you fill in empty spaces as {"", 0} rather than just
{""} to avoid compiler warnings about missing initialisers?

3. It would be good if it were possible to use a typedef so that the return
type of the external function can be "T" for some type T, rather than being
forced to be "struct T", as it seems to be at present. This means that
"struct T" has to be used everywhere else too.

4. I'm not sure whether this is a good idea, or whether it should be solved
by using C inclusion (as it can be), but it'd be nice if the generated .c
file included a prototype of the exported hash function, again, to avoid
compiler warnings (with -wmissing-prototypes under gcc).

This is all just fiddling to make building the code neater; it doesn't have
anything to do with the correctness or performance of the code, which seems
good.

-- 
http://sc3d.org/rrt/
Reality is what refuses to disappear when you stop believing in it (Dick)