Sylvain Beucler <[EMAIL PROTECTED]> writes: > unistd.in.h replaces 'close' by 'rpl_close' (when the replacement is > enabled), so this also renames the struct member.
Is that a real problem? Why does it matter what the struct member is called, so long as the program always calls it by the same name? I'm asking because, if this is a problem with gnulib, it is likely a problem with other platforms like Solaris, which are not above putting things like "#define open open64" in their standard header files.
