Re: glob: compilation error due to 'restrict'

[Bruno Haible]

Paul Eggert wrote:
> > Which fix to choose? Which one is likely to please the glibc developers 
> > better?
> 
> Let's keep the K&R syntax please.  Other glibc developers prefer that
> for some obscure reason (for external functions only).

Thanks for the advice. I'm applying this:

2007-03-15  Bruno Haible  <address@hidden>

        * lib/glob.c (glob): Add 'restrict' so that prototype matches the
        declared prototype. Needed with cc on OSF/1 5.1.

*** lib/glob.c  22 Feb 2007 23:33:19 -0000      1.14
--- lib/glob.c  16 Mar 2007 00:34:16 -0000
***************
*** 212,221 ****
  GLOB_ATTRIBUTE
  #endif
  glob (pattern, flags, errfunc, pglob)
!      const char *pattern;
       int flags;
       int (*errfunc) (const char *, int);
!      glob_t *pglob;
  {
    const char *filename;
    const char *dirname;
--- 212,221 ----
  GLOB_ATTRIBUTE
  #endif
  glob (pattern, flags, errfunc, pglob)
!      const char * restrict pattern;
       int flags;
       int (*errfunc) (const char *, int);
!      glob_t * restrict pglob;
  {
    const char *filename;
    const char *dirname;