Hi Sam, > Why does close depend on fclose?!
The justification was in <http://lists.gnu.org/archive/html/bug-gnulib/2008-10/msg00201.html>. > It seems that, close being a system call and fclose being a C library > function, the dependency should be the other way around: fclose should > depend on close, but _NOT_ vice versa. Yes, 'fclose' also depends on 'close'. > E.g., CLISP uses close but never FILE or fclose et al, so, when pulling > close, which pulled fclose, I got all these files which I will NEVER need The assumption was that the vast majority of programs use stdio and fclose(). But I agree with you, it would be more in line with the gnulib principles to let the programmer who needs specific features from fclose() to explicitly request the 'fclose' module. Any objections to removing this dependency? Bruno -- In memoriam Pancho Villa <http://en.wikipedia.org/wiki/Pancho_Villa>
