[lkml]   [1997]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject#include <config.h>
I see in various files that the "#include <config.h>" is not the first
Linux-specific #include in some source files. (See fs/proc/array.c,
where I got bitten by this.) The result of this is that if a new
configuration dependency is introduced into a header file, it is quite
possible that some uses of that header do not have access to the
correct configuration information, causing problems.

I propose that:

(1) The #include of config.h should be the *first* Linux-specific
#include in *all* source files, or

(2) There be declared some specific policy that header files should
not be sensitive to the configuration, or

(3) There is something else going on that I don't understand.

Can anybody comment on this?

Dale R. Worley Ariadne Internet Services
Voice: +1 617-899-7949 Fax: +1 617-899-7946 E-mail:
"Internet-based electronic commerce solutions to real business problems."

 \ /
  Last update: 2005-03-22 13:38    [W:0.034 / U:0.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site