changeset 8277:5aa192831f07

Gnulib doesn't impose ordering constraints between include files, except for <config.h>.
author Bruno Haible <bruno@clisp.org>
date Fri, 02 Mar 2007 01:18:28 +0000
parents 0ead70460e39
children a461304a8e77
files ChangeLog doc/gnulib-tool.texi
diffstat 2 files changed, 9 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2007-03-01  Bruno Haible  <bruno@clisp.org>
+
+	* doc/gnulib-tool.texi (Initial import): Remove paragraph about
+	include ordering constraints.
+
 2007-03-01  Paul Eggert  <eggert@cs.ucla.edu>
 
 	Followup to the 2007-02-12 patch, using suggestions from Bruno Haible in
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -235,10 +235,10 @@
 @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