bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

how many #includes?


From: Karl Berry
Subject: how many #includes?
Date: Wed, 15 Nov 2006 13:58:34 -0600

I made another pretest of hello, ftp://alpha.gnu.org/gnu/hello.  The
only changes are the ones reported here.

When running gnulib-tool --import or --update, there is quite a
long list of #include's.  The only modules I've actually specified are
closeout getopt gettext.  I imagine that many of the others come from
dependencies.  But the "top-level" includes all include whatever is
necessary, don't they?  

gnulib-tool says you "may" need to include:
  #include <getopt.h>
  #include <stdbool.h>
  #include <unistd.h>
  #include "__fpending.h"
  #include "close-stream.h"
  #include "closeout.h"
  #include "error.h"
  #include "exit.h"
  #include "exitfail.h"
  #include "gettext.h"
  #include "quotearg.h"
  #include "xalloc.h"

But my system.h only has:
#include <getopt.h>
#include <unistd.h>
#include "gettext.h"
#include "closeout.h"
(and a few other ANSI headers).

And there have been no complaints.  hello.c does not directly use
quotearg or fpending, etc.

Would it be reasonable/possible to have gnulib-tool output only the
top-level #includes?

Thanks,
Karl




reply via email to

[Prev in Thread] Current Thread [Next in Thread]