Bruno Haible wrote: > Hello, > > On MacOS X 10.3, one gets this warning: > > mkstemp-safer.c:34: warning: implicit declaration of function `mkstemp' > > The reason is that mkstemp is declared in <unistd.h>, not <stdlib.h>, on > this platform. But for POSIX compatibility, only gnulib's <stdlib.h> should > be sufficient to declare the function. I'm applying this:
Just a question: is including "unistd.h" the right approach? Not clear to me that pulling in all of unistd.h is the right way since that means ``#include <stdlib.h>'' implies ``#include <unistd.h>''. Probably the easiest solution,.... It's almost tempting to look at fixincludes, but on second thought that would undoubtedly bring in way too much baggage. Way too much.
