From 2d89ffe89df190659e2a0a396d06ed722ddc9b4c Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Fri, 2 Mar 2007 01:18:28 +0000 Subject: [PATCH] Gnulib doesn't impose ordering constraints between include files, except for . --- ChangeLog | 5 +++++ doc/gnulib-tool.texi | 8 ++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 44344c823..0ace3f213 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2007-03-01 Bruno Haible + + * doc/gnulib-tool.texi (Initial import): Remove paragraph about + include ordering constraints. + 2007-03-01 Paul Eggert Followup to the 2007-02-12 patch, using suggestions from Bruno Haible in diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi index cb37964a5..a7f6ca7fe 100644 --- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -235,10 +235,10 @@ file. That way, for example, if @file{config.h} defines @samp{restrict} to be the empty string on a pre-C99 host, or a macro like @samp{_FILE_OFFSET_BITS} that affects the layout of data structures, the definition is consistent for all include files. - -You should include Gnulib-provided headers before system headers, -so that Gnulib-provided headers can adjust how a system header -behaves. +Another reason why @file{config.h} must be included before any other +include file is that it may define macros like @samp{_GNU_SOURCE} +or @samp{_FILE_OFFSET_BITS} which, on glibc systems, have an effect only +if defined before the first system header file is included. A final word of warning: Gnulib currently assumes it will be responsible for @emph{all} functions that end up in the Autoconf -- 2.11.0