Bruno Haible <[EMAIL PROTECTED]> wrote: > Eric Blake wrote: >> Hmm - should we provide a gnulib <errno.h> that guarantees all of the >> standard errors, rather than doing an ad-hoc definition of EOVERFLOW and >> others in every place where they are used? > > We already have an EOVERFLOW replacement macro in m4/eoverflow.m4. It would > be better to use it rather that the current ad-hoc approach which > - defines EOVERFLOW sometimes to E2BIG and sometimes to EINVAL, > - ignores the hidden definition on OSF/1. > > I'm adding a new module 'EOVERFLOW'. This allows to remove the idioms from > the lib/*.c files. I applied this. > > Jim, is it ok to do the same for the 'getugroups' module?
Sure. Even if it's ever invalid, at least that use in getugroups.c will never be exercised.
