Re: Convert libiberty to use ISO C prototype style 3/n

[Gabriel Dos Reis <gdr at integrable-solutions dot net>]

DJ Delorie <dj@redhat.com> writes:

| > I think it is a logical part of the conversion and there OK.  But, you
| > might want to hear from DJ before that.
| 
| I agree it's appropriate for this conversion.  We may need to revisit
| this paragraph of the gcc documentation too:
| 
|         * Use of ISO C style function definitions.  This warning
|           intentionally is _not_ issued for prototype declarations or
|           variadic functions because these ISO C features will appear
|           in your code when using libiberty's traditional C
|           compatibility macros, `PARAMS' and `VPARAMS'.  This warning
|           is also bypassed for nested functions because that feature is
|           already a GCC extension and thus not relevant to traditional
|           C compatibility.

Completely agreed.  I'll prepare a patch for that, onece I'm finished
with the conversion.  Especially, at this point I don't know whether
regex.c should be first modified in glibc and then resynced with GCC
-- I had a quick look at glibc sources and I was under the impression
that the source codes and structures have diverged.

-- Gaby